"Oh, it also tracks your every move and taps your smartphone's microphone, supposedly in the name of helping to root out unauthorized match broadcasts in bars, restaurants and cafes." #privacy #futbol https://boingboing.net/2018/06/11/spanish-football-app-turns-use.html
Google is trying to patent an algorithm from public domain
Peter Watts can throw around scientific details or quantities in his stories which would be natural for his characters, but are conversions an average reader would never have had to make.
It just dawned on me Wolfram Alpha understands these, can help you subtitle Watts the way his _Blindsight_ characters subtitle each other's lingo.
We live in an age of informational plenty.
@cypnk Oh, I don't disagree. If anything, this is a case study on how perceptions tend to stick - whether they are still accurate or not.
However, Microsoft has come a long way. I think that it behooves us to recognize and acknowledge that.
Otherwise we risk sending the message to other companies that we don't really care about them mending their ways, we'll still assume they're up to the same crap they were 10-15 years ago.
recommend checking out some short stories from the Freeze-Frame Revolution universe if you're in a mood for some hard sci-fi reading:
One thing I've learned over the years is that it takes a lot more skill to solve a problem by writing code that's simple rather than clever.
@jankoekepan Yeah, that's another point. Tooling is a non-insignificant point, and Git has been getting a lot of tooling.
I can see how a team of writers wouldn't want to worry with branching, merging, staging or anything else, and would just want something that works, right there, from the file explorer they're used to. Tortoise does that.
@jankoekepan Personal taste as well. Even for solo projects, git's workflow feels more natural to me.
I used SVN for over a decade. There was always someone who got tripped over by its branch merging - even if they were experienced.
Git's branching made sense right away. I don't think I'd go back.
This is all from a 4-month period at the end of 2017. I'd used it myself for years and had run an on-site instance for a different team before which, albeit quirky, behaved much better.
Not sure what happened with them. Maybe it all got borked on the rush to add new features, maybe we joined at a bad time.
For a team willing to pay but which needed it to be plumbing and "just work", Gitlab fumbled every chance we gave them.
Some notes on #Gitlab, in case you're considering it:
- Usability is OK;
- SLA was a joke. We were paying for silver, but we didn't get replies to issues for days/weeks unless we raised a ruckus on Twitter;
- That doesn't mean the issues were solved, just acknowledged;
- Build runners may or may not start, depending on the weather;
- When we decided we going to self-host it, we found the export/import was broken, was a known issue for months, still unfixed.
It was a mess.
Having said that, I had to work with GitLab recently, and it was a nightmare. It's just trying too hard to be too many things at once & failing to be a serious contender for any of these purposes.