What people dislike is the boom-bust cycle inherent to all levels of a market economy. During some years, these companies suck people up like a vacuum -- that can be bad if you're on the inside and all of a sudden the culture goes out the window, or if you're expected to onboard 3-4 people at the same time, or you end up with a reorg every quarter. Then, on the other end of the spectrum, companies shut down (non-backfill) hiring entirely and layoff huge percentages of the company, with no guarantee that you'll be safe just because you're doing a good job.
Human lives do not work like this. If you're getting married, if you have an unexpected hospital expense, if you want to buy a house -- these are not things that "market cycles" will plan around, but you have to.
Being quick to hire or fire is not the problem. Massive overhiring and massive layoffs are.
> Assembly to Python creates a lot of Intent & Cognitive debt by his definition, because you didn't think through how to manipulate the bits on the hardware, you just allowed the interpereter to do it
I agree! You often see this realized when projects slowly migrate to using more and more ctypes code to try and back out of that pit.
In a previous job, a project was spun up using Python because it was easier and the performance requirements weren't understood at that time. A year or two later it had become a bottleneck for tapeout, and when it was rewritten most of the abstract architecture was thrown out with it, since it was all Pythonic in a way that required a different approach in C++
I’m not sure the GP did mean that, but I agree it’s a much better solution than maintaining an out-of-tree kernel module, which is generally a really bad idea
In Fil-C, currently, all stack allocations that “escape” need to be allocated in the heap.
“Escape” is defined very loosely; it currently means: some function other than the one that owns the stack allocation needs a pointer to that allocation.
For example even if you could prove that `bar(Value* p)` never stashes p anywhere, the fil-C compiler will currently heap allocate that value anytime bar is called. The one exception is if bar had already been inlined, and so from the FilPizlonator’s perspective there isn’t even a call.
This is clearly dumb and fixable. It’s dumb because lots of functions aren’t worth inlining but their body is analyzable. Slow paths are like that. It’s fixable because those slow paths - and lots of code like them - takes ptrs as arguments and then obviously just uses them for loads and stores but doesn’t escape them any further.
You’ll sometimes hear me say that Fil-C is nowhere near as optimal as it could be. This is just one example of that
Clearly they don't. They don't tend to occupy other countries, not outside of immediate territorial claims like Tibet (if you think that constitutes an "other" country)
> whether ... the concept of "bad actors coming in and ruining it for everybody by taking without giving back" even makes sense.
This is pretty clearly answered by the GPL: yes, it does, and this concept has been around since the very beginning.
> The information is still there
True
> as is the community that you've built
Untrue. At this point it's well understood that AI is substitutionary for many of the services that would have once afforded people a way to monetize their production for the community. Without the ability to make a living by doing so, even a small one, people will be limited to doing only what they can in the little free time they get outside of work.
That's the whole problem -- that AI, as it exists today, is taking away from the public, and hurting it at the same time. That's closer to robbery than it is to "sharing in the community".
> The last time a property class was removed was _slaves_.
Easy counterexample: titles of nobility. Also perpetual bonds, delegated taxation rights, the ability to mint currency. The list goes on.
If you're going to use history to support your AI bull agenda, you should at least pre-fly it with the AI first -- it would have pointed this out.
> Arguing that copyright is good because a subset of big tech doesn't want it around is as stupid as arguing that slavery is good because the robber barons don't like it.
Sorry, who's saying it's good? You are, actually, insofar as you're willing to support the right of AI companies to take people's information and use it to create copyrighted model weights. Why do you care less about the intellectual property of billionaires than that of the common man? Do you really think they're on your side?
reply