I think the difference is that they expect to not break tests most of the time. So most of the time this just saves time.
It’s like when you merge a documentation PR while the tests are still running: You’re pretty sure that the tests won’t break. With this solution however you’ll still be pinged if they do break, later.
The whole point of the UI is so that your workflow is simplified without having to understand the exact inner workings of it all.
GHDesktop’s simplicity means that most of time I don’t have to call 4 commands to just check out a new repository or PR because one click runs all those 4 commands and more.
As simple as it is, lately I rarely have to use the CLI (which however I still use because I rebase and fixup)
The fact that “takes you away from the terminology” sounds like people complaining that Windows 95 users don’t know what MKDIR means: That’s the whole point of UIs.
Technically it’s a family business that I grew up into and I ended up being a developer because at 14 I made the restaurant’s website with Macromedia Fireworks and Dreamweaver.
Bad for so many reasons (including abuse of GitHub issues, spam, and the ability to change the URL the short link points to)
If you want your own private shortener, I have a better idea:
Use GitHub Pages and create a `/1/index.html` (where 1 is the short link name) and add a “refresh” meta tag in it. Completely static and no build/JS necessary.
This could be opened up to others by combining it with issues and GitHub Actions, but who wants that?
Another better idea for a private URL shortener is hardcoding a list of URLs in a CloudFlare Worker. Much faster and with real 301 redirects.
That’s the issue. Linux runs everywhere and is not a consumer product, that’s why I exclude it.
Until you can build your own general-purpose PC and can decide to make it ARM, it will not be considered an equivalent option, it will just be another tablet, “chromebook” or “board for hackers”
Restaurant owner in Italy here: We usually don’t offer pizza at lunchtime because it takes time and wood to fire up the oven and keep it at temperature. Low request volume means it’s not worth it, at least for small pizza places.
If you want pizza for lunch you head to a bakery or “bar” and they have squares (not “slices”) ready for you to pick up.
Is there anyone shipping an ARM motherboard and ARM chip? I think the "openness" is also defined by what the market offers. All I see are non-extendable notebooks.
Also until you can run non-linux "desktop software" on one, it will always feel like a "tablet"
I’m ok with this. The alternative solution would be to kick the hotel off of TripAdvisor.
As a business (TA) I wouldn’t want to have to deal with troublesome properties, honestly. This action would be a good enough deterrent from others to follow the lead of the resort.
On one hand, if users aren’t comfortable leaving bad reviews, the site will only show high scores.
On the other hand, if you want to be the review platform, people can’t think you can’t handle negative reviews.
Sounds like a bad deal, comparatively. Microsoft skips the low-level interfaces but gives you redundancy and usable UIs and services (on top of an API)
10mb per file only if you average videos, multiple sizes/formats and assume some redundancy. The single photo file stored by Google averages 2 megabytes.
I’m not completely familiar with Amazon reviews, but if I remember correctly it’s not super clear that you’re reviewing the product and not the seller, and how to review the seller specifically.
This difference is irrelevant when the seller is Amazon, but very relevant when it’s not. We all know how Amazon blurs this line, so the confusion is understandable.
That said, I hate it too, and it’s Amazon’s fault.