That period rapid saw automation and reduction of cost of many, many peoples' livelihoods, but society is unarguably better for it. Eventually people were freed up to do higher-order work.
301 karma · joined May 15, 2016
That period rapid saw automation and reduction of cost of many, many peoples' livelihoods, but society is unarguably better for it. Eventually people were freed up to do higher-order work.
I suppose if you're not actually showing it to anybody it becomes rubber ducking via design document.
By this I mean put as much of your core logic and functionality as possible into a shared library, and then make a separate Swift/WinForms/whatever codebase for the UI of each native platform you want to target. Each UI app would call into your shared library.
There is a bit of duplicate work in making separate UIs, but the UX is far superior (IMO) and you have the advantage of not needing workarounds or plugins to access platform-specific features.
Happens to be that a globally distributed network of endpoints is also pretty great for absorbing DDOS attacks, so they started offering that too. And then I guess they parlayed that further into offering other T1/T2 level Internet services too.
I don't use them for CDN / DDOS but I do use them for other things and I think they're great.
If your goal is profit, don't open source your core product.
We've seen this time and time again where a company releases their core software under a permissive license, and then bigger competitors come along and resell a solution redistributing their software.
If the company's central goal is profit, this is an existential threat. However if your company goal is to ensure the software exists (as a non-profit steward), this is a resounding success!
This doesn't apply to software that's secondary to your core product, e.g. a useful tool you've developed but don't make money directly selling to others.
However Colossus _does_ run on the general Google compute infrastructure, and so needed a way to get CPU/RAM quota where none existed (because it was all used by existing, non-storage users).
It's a dirty trick IMO, but it has seen some mixed success.
One added benefit is it serializes/deserializes safely (even when you add / remove values), so you can persist and read back values without a problem - even to a different language.
One example of an intriguing idea I heard discussed on a podcast - imagine you're watching a streamer on YouTube and think the game is cool. If it were integrated with Stadia then with one click, you could be playing the game! In browser! Maybe even playing with the streamer (for multiplayer)!
So much potential wasted...I can only shake my head.
It seems like you're talking about team nimbleness and cohesiveness, which I want to say is orthogonal.
That's my major problem with it; it locks you out of messing with your own machine data, which you can see being instantly abused by third parties to prevent modifications.
It's not a smashing unicorn success but it's definitely a success.
One of my colleagues maintains a Windows box at home, and tells me he hates opening the thing because whenever he does the OS gives him "chores" to do - you _must_ update this bit, you need to listen to this offer, etc. Like, you're the computer and I'm the human! I give you the work, not the other way around.
Anyways, the sum of my rant is I finally switched to PopOS. It's been surprisingly smooth, especially with Proton making Linux gaming so easy. If anybody is thinking of doing it, now's the time to try it out.
I don't think this is a search problem, I think Google is legitimately surfacing what's available on the Internet for given query. I think this is the dead internet theory at play, and that there just isn't anything valuable to show!
People who would (in the past) run their own website or blog now post that same content on social media, which is why Reddit has become mandatory for people looking for genuine opinions.
So you start by just doing a visual scan of all the caps on a board to see if any are bulging? If nothing is apparent, where do you go from there?