Funny this popped up...I've been looking at replacing our slow and flaky Selenium test suite recently.
From what I can tell here are the benefits:
* With Playwright you don't need to put manual waits in your program. It's async.
* You also don't need to keep updating the Selenium.Webdriver to stay in sync with your browser version. This is a 15-20 minute time sink each time it happens.
* Can run in headless mode which will run the test suite much faster than selenium.
* Also appears to have better command line options to be run from a CI/CD environment
Where is the data for this stored? I was inspecting and didn't see anything in Local Storage, Session Storage, nothing on the network tab. Hit refresh thought everything would be wiped, but all my data was still there!
Unfortunately I sent the whole thing back to the repair shop and I'm guessing they probably sold it. In hindsight I should have taken it out prior to sending it to them...
I had the same issue with my MacBook Air with the exact specs, though I never dropped mine. Just shut it off one night after watching Thrones for a few hours and it never turned back. Pleaded with Apple for quite a while to see if they would replace the logic board due to defect, but they did not. Mine was purchased in May 2013 and dead Nov 2014. Finally broke down a couple of years ago and bought a low end I3, with 4gb of ram logic board and it's working again. Guess I would have tried this as well had i known it was an option at the time :)
Were a team of 40 and we are using teams. It does work pretty well for most things, and I like all of the integration options. We had been using Mattermost prior to switching and a few of us still use that instead. The biggest issue I have with teams is the markdown support is not good. It tries to format as you type instead of letting you type markdown and have a type/preview mode. I've raised this on their forum and it doesn't appear to be anything they want to fix either. If they fixed that issue I wouldn't have any complaints.
I've been managing a small instance since version 5. There have been a few hiccups here and there, but mostly due on my part to not reading the release/upgrade notes carefully enough. Since version 8/9 it has been absolutely pain free. Run apt-get update then apt-get upgrade wait a bit and enjoy the new release!
SublimeMerge is also a wonderful tool. Been using that since it came out and has helped tremendously with difficult merges. It's lightning quick as well.
Similar to magit - Sublime Text also has SublimeGit, not as fast as SublimeMerge.
Visual Studio Code built in git functionality is also nice.
I second this as a owner of a bricked 2013 MBA with a dead logic board. Bought a Lenovo T430S for $450 a few years back and couldn't be happier with it. Never buying Macbook again.
We've been on Gitlab since version 5 and for the most part it's been a pleasure to work with. The omnibus version has made things way easier to install/upgrade, so not sure what the fluff is about being hard to maintain. The UI is adequate and they are working on improvements to smooth out the rough edges a bit. Looking forward to the improvements and new features to come. Just wanted to post something positive instead of the nit picky hate I've been seeing lately about Gitlab...
Having an upstream can be useful for CI testing and for deployments with tools like Capistrano. Plus it allows you to pull down your code from other environments if needed and acts as a additional backup, so there are potentially lots of reasons to have one.
Anyone have a clue as to what were supposed to be able to do with this "Windows: Added command line helper, subl.exe". I'm guessing it's mainly for a shorter exe name to add to your path when launching sublime from the command line, but maybe I'm missing something?
I would argue that React is closer to a library than a framework. It's a small library with some useful functions for making web components. It helps by removing a bunch of boilerplate code that you would have to re-write with each new app. The thing that it doesn't do is hold you hand and tell you exactly the way things should be done as some of the other frameworks do.
Really depends on the type of product, if you know it's something that the whole world would benefit from then maybe build first makes since, but if your targeting a niche market then for sure you want to get a barometer if your product is going to be needed and what the biggest pain points of those who would use it are.
If you've dealt wih servers and played with rails it should be pretty trivial for you to set up gitlab. Remember it's open source so before you say it's too hard there are paid alternatives that have one click installers.
Gitlab is a fantastic project and it would be worth the time getting it installed.
From what I can tell here are the benefits:
* With Playwright you don't need to put manual waits in your program. It's async.
* You also don't need to keep updating the Selenium.Webdriver to stay in sync with your browser version. This is a 15-20 minute time sink each time it happens.
* Can run in headless mode which will run the test suite much faster than selenium.
* Also appears to have better command line options to be run from a CI/CD environment