that just means they might not be actively looking to join cloudflare but are willing to do it if the price is right. nothing wrong with that, it's how employment works for the most part. likewise retention in these cases is typically solved via golden handcuffs, another "the price is right" thing.
that's an interesting reflection on the nature of open source - in theory the source is there and "the community" could conceivably continue development. especially in the case of something like deno where the people most motivated to keep it alive are already programmers. but the reality is that however distributed an open source project is in theory, in practice it needs a single entity to steward it, otherwise it will die.
hopefully that single entity can be a consortium of companies invested in using the runtime, sort of like opentofu recently.
honestly I would rather not have a personal website than be beholden to some big company to host it and have to worry about what random crap they would pull via some flaky automated ToS enforcement.
to get some intuition about why this is such a big deal, look up the history of strassen's algorithm, which solved matrix multiplication in less than O(n^3). this was a truly stunning result because it seemed intuitively obvious that the output matrix had n^2 cells each of which was calculated via an independent O(n) loop over a row/column of the input matrices, so how could you do better than n^3. but once strassen proved that you could do some clever tricks and reduce the overall time to something less than O(n^3) it started an entire cottage industry of people getting better and better algorithmic bounds. the initial breakthrough was a qualitative one, independent of how much it improved things in numerical terms.
lately I've been thinking about how something on reddit/hn/lobsters reminds me of an interesting moment from my career, and I write up a small reply about it, and that could conceivably also be a blog post if only I had a blog. and then I do nothing about it :) but that's definitely one way to blog; just take the effort to follow through on random inspirations like that.
another great route to follow is what julia evans does on her blog [https://jvns.ca/] - a lot of the posts are "hey, I learnt something new today, and here it is!". the key point is that there is no attempt at having every post be the same "weight", some of them are deep dives into a topic and some are just passing thoughts or howtos.
that looks very interesting. if it's targeting the electron/sciter market I would encourage you to put the binary size and memory footprint in the readme so people can see where it lies on that spectrum - it's one of my top priorities when evaluating a desktop app library.
every time I see this argument I think of the fact that one of my current side projects is written in D with qt bindings off github - an obscure library for an obscure language - and claude had zero issues with it. I had to guide the architecture pretty heavily, but the fiddly bits of interfacing multithreaded c libraries to D's garbage collector and qt's event loop were all thanks to the LLM, and done a lot quicker than I would have.
bounds checks are one, yeah, but I was also thinking about the tricks c++ could play with optimising undefined behaviour, as well as unsafe patterns involving shared access and pointer aliasing that a human could determine was safe in that specific case but that the rust compiler would balk at. and maybe it wasn't actually safe in which case the rust code would have the last laugh.
tbh while the astra announcement in that link had some good stuff it was scattered through so much boilerplate marketing speak that I had to force myself to read it and look for the content. I found the gemini blog post in the OP a lot more readable and engaging.
but that's a side issue; my main point is that you are underrating the impressiveness of getting a safe rust port of a highly optimised c++ library even nearly up to par with the original. the tradeoffs rust makes for memory safety cost it some of the raw speed of c++ even with all the zero cost abstractions and purely compile time guarantees they have. (tangentially i wonder if ats (https://www.cs.bu.edu/~hwxi/atslangweb/) would be a good candidate for LLM assisted ports; it seems way more advanced than rust and might actually get c-level performance with safety, but it's really hard to write.)
there was already an optimised c++ library and a rust port that was safer but less performant; they managed to get a new rust version that recovered a lot of the performance gap. sounds pretty damn good to me!
I have never understood the whole "this is a winner take all game" mentality - the sheer size of the pie is so great that from a purely rational standpoint companies should just be trying to productively get a slice of it and be profitable. winner-take-all is just greed/capitalism run amok, where it is not enough to be profitable, you have to own the entire market (and presumably extract rents)
grew up in dubai in the 80s, and we went to a beach in fujairah once which had not just a wonderfully starry sky, but the most amazing bioluminescence in the ocean. don't think i've experienced both things together since then.
by "inventing" they mean that no one higher up in the org is going to tell you what your team needs to be working on, you need to do user research and discover the issues for yourself, and then come up with the right set of features that will solve those issues.
the pacing and consistency are atrocious, unfortunately. I loved the first six books, hated the seventh, and straight up abandoned the series halfway through book 8. tempted to do a full read through now that Sanderson has completed the series in a way that people seem happy with but it's a lot when I know I'm going to run into at least those two bad books in the middle and possibly more after that.
I'm on book 3 of Romlyn Domingue's "Keeper of Tales" trilogy. One unusual touch I liked is that each book is written in a different person - book 1 is a second person autobiography written as the protagonist talking to her past self, book 2 is third person with a different protagonist, and then book 3 is a continuation of book 2 but with the voice switched to first person.
what you are arguing for is objectively extremely bizarre. if you take a step back, this is what is playing out: company C makes a device. it needs an operating system to run software, so they add it. if there was no operating system the device would be useless and no one would buy it. now person A buys said device. it's theirs, they have paid money for it, they own it. person B writes some software. it runs on the device's operating system. they want to sell it to person A. person A wants to buy it from them. why should company C be involved at all? I found this super weird and distasteful when game consoles were allowed to use this business model, and am even more taken aback that general purpose computers get away with it.
> I think I'm a pretty skilled programmer, or I'm at least good enough at interviewing to convince other people of that, but it's pretty obvious from comparing LLM generated code to code I'd write myself that in many domains LLMs are superior to me.
there's an important caveat here - LLMs absolutely can write better code than me, but they can also write far worse code, and often don't seem to be able to tell the difference. I find myself spending a lot of time prompting the bots to refine their code in specific ways that I only know about because I read the generated output.