654 karma · joined June 21, 2011
But once out of a call you end up in a messy maze of random cluttered functionality and different, confusing styles of chat options, integration with a bunch of stuff that on paper sounds like a good idea, but in reality is annoying as hell and hard to navigate.
Ownership is based on the ability to have something tangible of a limited supply, but as I established before, digital assets can be freely copied. What are you trying to do? Artificially limiting this? Trying to push through a completely new idea of 'ownership'?
The only thing owning an NFT gives you is bragging rights of a perceived ownership. But if I say "I don't recognize this NFT proving anything", copy your asset, reproduce it and sell it somehow, you can't stop me. You claim to own some bits and claim to be able to prove that, but I can just ignore that completely, since there is zero legal grounds for this.
This is why it is absolutely moronic in my mind to have an 'ownership' idea on digital assets. It's already bad enough in online games to have in-game assets, which is in a walled-garden, under control of the company making the game, so yeah, there they can do this, it adds some perceived value. But to actively introduce this concept in an open digital world sounds absolutely crazy, counter-productive and conceptually against everything my ideal version of the internet would be: open and free as in beer.
That already happened, but with no negative impact on its public/free side. All we got from it are unlimited private repos, and limited github action minutes and repository storage in the free tier. I call that a win.
Also, the GitHub sale was 2.5y ago, if things would have gone wrong, we would have already seen the cracks.
Ruby devs abandoning GH is simply because they saw the writing on the wall that Ruby was not seen as long-term viable tech by MS. And from a sysadmin/SRE/devops pov, if there is one stack I hated supporting more than JVM-based deploys, it's Ruby, so I wouldn't blame them.
The whole situation has seen mainstream media attention here, which helps a lot I guess.
And then doing stuff like this:
> When Amazon announced their Open Distro for Elasticsearch fork, they used code that we believe was copied by a third party from our commercial code and provided it as part of the Open Distro project.
That makes it all the more dodgy. The fact that AWS is also the only cloud provider they complain about, and explicitly name others where they don't have these issues with, paints a pretty clear picture imho...
No, because it's offers one of the most consistent UX. It's far from perfect, but Apple manages to make this happen on both iOS/OSX.
Of all the projects you mention however, only Toshi addresses clustering, and as an experimental feature.
If you're using it for logfiles, the only real alternative I know is Grafana's loki.
Also by people who know that what they were doing was straight-up illegal in a lot of countries, and grey-area in a lot of others. So this was a real risk.
Parler on the other hand, at its core was just a social network, and if you look at the founders/owners, they have a very disconnected interpretation of "free speech", so they were clearly thinking nothing bad could happen.
This is the reason modern active bookshelf speakers like the Klipsch The Fives punch way above their weight and pull off stuff its hardware shouldn’t be capable of.
Apple can do the same thing, they have the engineers and know-how. And on top of that, the positional audio is something that requires compute power anyway.
In Europe, where debet-cards are the de-facto standard, most online shops use a payment aggregator, which forwards your payment request to your online banking platform of your own bank, which you then have to confirm. Sometimes using a cryptographic challenge/response from the chipcard, but more and more just by using your phone and banking app to scan a QR code and validate the payment there.
This completely side-tracks the insecurity of creditcards, there is nothing to steal.
The biggest incident, if I remember well, was related to the layerfs stuff, which was supported by Ubuntu, but which RH refused to include. Instead they pretty arrogantly pushed to merge a PR which was breaking other stuff in Docker, and were pissed when the maintainers refused to. That whole thing obviously rubbed people working on Docker the wrong way, which was the beginning of the pretty sour relationship.
After that I don't think there was a lot of goodwill from Docker towards RH, probably causing a lot more issues..
Docker is not yet available - but even when it would become available, emulating virtualised x86 code is explicitly not going to be supported. That in many cases means pulling a docker image built in a ci/cd pipeline where a dev screwed something up and debugging it locally is no longer an option. If I wasn't freelance, I could probably get away with some cloud instance to run all my docker stuff, but I'm dealing with too many different environments, for clients with various different legal requirements making this simply 'not an option'.
Too bad, because the machines look very promising for everything else. Development tools aren't there yet, but I expect that to be fixed pretty quickly.
There are caching issues, and you need decent metrics and tracing across your entire platform to have any idea what's going on.
My natural sleeping rhythm always seem to drift towards 3-4 -> 12 in weekends or when I take a few days off.
TSMC has to spit out Zen3, RX6000, plus the custom versions for XBX and PS5, all around the same time...
Microsoft goes where the money is. They want developers to target their platform(s), and native Windows applications are a dying breed, everything is moving to the web/cloud, which is where Azure - and let's not forget Github - comes to play.
A ton of the development targeting the web had moved to Mac, the same time they completely missed the mobile app train, which meant they effectively lost an entire generation of new developers, not familiar with MS or even wary of them.
Introducing better and free developer tools on every single platform under the Microsoft branding introduces many developers to them again, with a positive impression. Which suddenly opens doors for Azure. It's the same reason they now have WSL2 on Windows running a real, heavily customized kernel. They want developers to feel comfortable using Microsoft, so Azure has a better chance. A developer having a good experience with "Microsoft" VSCode and coding in it daily won't be shouting "M$ SUCKS! Azure sucks!" as quickly, and that's where it starts.
And you see a big push of MS in the enterprise world of moving clients to Azure, and they don't care what platform you're using. If you're big enough, they gladly send a bunch of engineers to introduce your developers and infra guys to Azure, and they don't care if you run Windows, Mac or Linux, all their tools surrounding this are all cross-platform. At a client of mine's R&D department, this happened while I was there, and they didn't care that 3/4 of the tech people there were using Macs. Their guy who came in to introduce k8s on Azure even had a Mac a big Linux penguin sticker over the Apple logo, surrounded with various stickers of cloud-targeted opensource software. When I asked him about that, he responded with something like "well, they don't care, although I probably shouldn't add RedHat sticker".
So as long as "the cloud", which Linux dominates, makes Microsoft money, they don't care. And given the situation we're in, I doubt they'll ever be in a dominant position there to allow them abusing their power like they did on the PC desktop market in the 90's and 2000's.
I think the core reason for their success is a deep understanding of the problems their core audience - gamers - was facing. Gaming is organised in communities, and it was built around that. It solved multiple issues for them, mostly - it made interacting fun and easy. It supports emoji, is meme and web-friendly, organising to play games together is made easier, you can see who's playing what, built-in voice-chat, moderation, ... Barrier of entry was also very low, you could just use the web-client, no need to install. But it also works on mobile, which makes it work for console gamers too.
Until discord came along, you could do all these things by combining different tools, but never as good, and having to deal with multiple tools made the barrier of entry way too high. When I was younger, a gamer had to be someone somewhat technically skilled. IRC, ip addresses, dedicated servers, ... made it all a lot harder to get into. Gaming however is very mainstream these days, and it keeps surprising me how small the the average gamer's technical knowledge is. And that's no a bad thing imho, gaming in the end is something to be enjoyed, no need for gatekeeping.
No idea what happened to it though... I suspect finding replacement parts for the things that wear out has become close to impossible, but I doubt that thing was broken in any other way.
That said, I always enjoyed watching MotoGP... Maybe should start following it again :P
There are almost fewer cars running on hydrogen on the road right now than there are F1 cars on the grid (only half joking), and while many mainstream manufacturers have made prototypes and concept cars even before they did anything pure electric, pretty much all of them have real full-electric products in their lineup, or at leat in the pipeline. There are some hydrogen pilot projects, sure, but I can't go to a dealer right now and order one. So going for hydrogen would be a really bad move, also because its energy density is inferior. The current ICE units in F1 are already at the upper-limit of possible efficiency, so replacing it with a fuel with a lower energy-density will be a step back in performance, with little or no future path to real improvements they don't have right now.
I'm an F1 fan, but I see that it is on a dead-end, one-way street. It'll take a while to reach the end, and as long as there's not a superior technology which can beat it on it's own grounds, it's not going away.
The "only" thing standing in the way of electric race-cars beating them is energy storage, which I expect to be improved at a break-neck speed in the coming years. FE has the advantage that this is the exact same problem affecting road-cars, which is why you see quite a few mainstream brands being attracted to it right now. But the energy density of oil-based fuels will be hard to beat, it will take a while before an FE car can beat an F1 car in every situation. But I'm excited for when this happens, since right now, FE fails to capture my interest for multiple reasons. There is no track-overview, all look pretty much the same to me, there are no iconic locations. Next year they'll finally be using the full Monaco circuit, which is a good start, and currently one of the very few viable F1 tracks for FE, but they have a long way to go.
However, now I’m on the operational side of things, and there are 2 types of applications I avoid to deploy/maintain, mainly because of their runtime: Java and Ruby apps. It’s very likely the Ruby runtime has improved, but we actually set up a haproxy with multiple instances of the same ruby app, which we just restarted every 2 hours, just to keep it running properly. Upgrading ruby back-then was a mess, and could break a lot of things. I can’t comment on the language itself, but the runtime left a very bad impression. I since then (4/5 years ago or so) have successfully avoided ruby, so it’s possible things have improved, but first impressions last...
> go (and garbage-collected languages/runtimes in general) may be poor successors to C and C++ for applications where consistent performance and memory efficiency are important.
I think the latter part here is indeed important. From my pov, Go is a lot better suited for a lot of the stuff I previously used C/C++ for, where a scripting language like Python was sometimes an alternative. I rarely touch C/C++ anymore these days (except for arduino stuff), and python, which I used a lot before, has become something I only use when I really need a dynamic language for some hacky stuff.
But languages are just tools, pick the best-one for your problem. Go certainly carved out it's niche, and Rust is also going pretty strong, and although maybe not as accepted, is also very interesting and promising.