Yes, it's an annoyance, not an insurmountable obstacle. If one is bothered by it, there's the hub gear, invented more than 100 years ago.
1,704 karma · joined August 12, 2015
Yes, it's an annoyance, not an insurmountable obstacle. If one is bothered by it, there's the hub gear, invented more than 100 years ago.
Now human programmers might find it more difficult to get certain things right than others, but to a LLM only quantity of examples matters, no?
The killer (hah!) feature is arguably its homoiconicity, allowing to modify the language easily within itself ("macros"). This has the obvious advantage that you can add missing features (usually) easily yourself; and exactly that causes headaches for those tasked with maintaining other people's code.
> Nowadays with LLMs writing all the code
Oh, you came all the way from the future and that's what you bring us?
Obsolete standard turns out to be insufficiently strict, news at 11.
Presumably one intends to debug the code, when setting (debug 3). Then it'll be helpful to see the stack, no?
> Another related footgun is deep recursion of other kinds, for example when recursively traversing down lists. For long lists it's easy to exceed the stack size limit. The common idiom is to recur on list elements, but iterate or map to go along a list.
Not going to argue with seasoned lispers here, but IMHO recursive code makes most sense when accessing recursive data structures.
Only those who try to maximize profits while skirting the risk of a revolt care whether global average temperature will be 1.2 or 1.8K above pre-industrial average in ten years. For the rest it's already too warm, the damage is already plainly visible.
We don't need better models to predict future warming; we dragged our feet long enough that we can now look at historic data to see where it's going.
I'm sure some of the more entrepreneurial minds will argue that many of those rules stifle innovation and progress. But also on a personal level, at least to this returning German, some of the rules seem silly at best and at worst cause some underlying sense of oppression. Why, e.g., is there a Meldegesetz/Meldeamt? I survived for 25+ years in California without such.
There are safety/freedom tradeoffs and whether they are worth it, everyone has to decide for themselves (at least Germans are granted the liberty to leave, if they don't like it). Many Germans long for a more adventurous life, but in the end most prefer to visit, rather than emigrate to, foreign shores.
It works, the user experience however might not be great. Latency is your enemy, as are occasional drop-outs. For remote connections outside a LAN, naked X11 isn't recommended. NoMachine's NX (or the shrink wrapped X2Go) were better suited for such.
And with "completely unaffected" you mean the internal (meta-data) consistency was maintained, recent user data changes were silently lost however.
That would be my guess too, the current batch however is all over the place: Bluetooth, file systems, etc. (the network layer ones are probably the most interesting ones). And the severity is mixed as well, some are 'just' vulnerabilities to potential DOS attacks.
> I expect distros to split less popular kernel modules into many separate opt-in packages
In the past questionable modules were blacklisted rather than removed.
Common Lisp, as an example, makes some deliberate flexibility (and elegance) vs. performance trade-offs. I'd think to speed Python up more than PyPy could, one would have to sacrifice some of its features (some of those might not be all that popular or even desirable).
Nah, Python has its place. If its performance isn't adequate for the problem at hand, rewrite the bottlenecks in C++ and be done. LLMs should make that easy, no?
Because you were busy working on that so urgently needed port of Linux to the Sega 32X?
Well, both are true of course. You will have to put numbers on those to make sensible decisions.
Historically, creating processes in Linux has been cheaper than in other Unix-like OS (you might find results of an old Byte benchmark) and much cheaper than in Windows. Creating a thread will be undoubtedly cheaper still, but whether that will change the user experience or is worth the cost depends on details (how large the memory footprint is, pagesize, how many files are open, how many threads are to be executed, their lifetime, how many execution units are available, etc.).
That distinction is important as pointers generally cannot be shared (a problem which can of course be solved with one more indirection ;-) .
I'm not at ease regarding LLM generated code changes to a project with a (hopefully) long expected life time, but LLM generated regression tests should be less contentious. I wouldn't expect them to be maintained much; rather, if they don't perform as intended against a future build, just have them recreated.
I wished the two phases would have been tackled in reverse order.
Who wants to contribute to an unmaintainable code base?