MaxBarraclough

7 ms·

61.
by MaxBarraclough 9mo ago
That's the point though, it doesn't reflect human usage of the word. If delve were so commonly used by humans too, we wouldn't be discussing how it's overused by LLMs.
62.
by MaxBarraclough 9mo ago
Technically correct, but not an issue in practice. If you want a licence that's approved by the OSI but not the FSF, or vice versa, you have to go looking for it. If memory serves there are no licences in the latter category, and the f
63.
by MaxBarraclough 9mo ago
Sounds like the Jevons paradox . From https://en.wiktionary.org/wiki/Jevons_paradox : > The proposition that technological progress that increases the efficiency with which a resource is used tends to increase (ra
64.
by MaxBarraclough 9mo ago
> A programming language is a formal specification language that we know how to compile Plenty of real programming languages are ambiguous in ways that surely disqualify them as formal specification languages. A trivial example in C: dec
65.
by MaxBarraclough 9mo ago
> A formal specification language is a programming language that we don't know how to compile. Not really, on both counts. Firstly they're not really programming languages in the usual sense, in that they don't describe th
66.
by MaxBarraclough 9mo ago
> It would only work if there's a sizeable, technically-inclined userbase of the project so that someone is likely to have audited the code. Not really. There's a long history of seemingly credible closed-source codebases turni
67.
by MaxBarraclough 9mo ago
> Open source is not synonymous with the GPL and most businesses try to avoid open source software when implementing their core competency. What you mean here? Businesses often implement their own core code, but they don't deliberat
68.
by MaxBarraclough 9mo ago
It's no guarantee, but it's a positive indicator of trustworthiness if a codebase is open source. I don't have hard numbers on this, but in my experience it's pretty rare for an open source codebase to contain malware. F
69.
by MaxBarraclough 9mo ago
I'm not convinced that lowering the barrier to entry to software changes will result in this kind of change of norms. The reasons for closed-source commercial software not supporting customisation largely remain the same. Here are the
70.
by MaxBarraclough 9mo ago
> In future everyone will expect to be able to customise an application, if the source is not available they will not chose your application as a base. It's that simple. This seems unlikely. It's not the norm today for closed-s
71.
by MaxBarraclough 9mo ago
For good measure here's a link to Dijkstra's The undeserved status of the pigeon-hole principle . https://www.cs.utexas.edu/~EWD/transcriptions/EWD10xx/EWD109...
72.
by MaxBarraclough 9mo ago
That's not the approach they're referring to, iOS doesn't support that. They're referring to delivering the compiled native code as part of the app package.
73.
by MaxBarraclough 10mo ago
> faster WASM and WebGPU Regarding WASM at least, it seems to depend. https://arewefastyet.com/
74.
by MaxBarraclough 10mo ago
The last link is broken. GitHub repo: https://github.com/howerj/muxleq
75.
by MaxBarraclough 10mo ago
From the article: > At this time an open source HDMI 2.1 implementation is not possible without running afoul of the HDMI Forum requirements. I wonder on what basis. Perhaps an obligation to ensure the software resists reverse-engineer
76.
by MaxBarraclough 10mo ago
> different people need different levels of explanation > the further a person is from understanding how the Linux kernel works, the more iterative the explanation will need to be Good points. Reminds me of how science is communicated
77.
by MaxBarraclough 10mo ago
> optimizing for speed You presumably mean prioritizing development speed , which is essentially the opposite.
78.
by MaxBarraclough 10mo ago
That's a little vague, I'd put that more pointedly: they don't understand how the C and C++ languages are defined, have a poor grasp of undefined behaviour in particular, and mistakenly believe their defective code to be corr
79.
by MaxBarraclough 10mo ago
I realise it's not a very substantial point, but it makes me wonder why ARM went with AArch64 rather than just officially naming it the obvious choice of ARM64 . ARM64 is both snappier and much clearer as everyone immediately know
80.
by MaxBarraclough 11mo ago
Agreed, and Google developers can probably be trusted to 'act responsibly', but too often people forget the distinction. Some Rust codebases are wildly unsafe, and too often people see written in Rust and falsely conclude it&#x2
81.
by MaxBarraclough 11mo ago
> I think both Mozilla and Google are OK with this - if it is written in Rust in order to avoid that situation. It would need to be written in the Safe Rust subset to give safety assurances. It's an important distinction.
82.
by MaxBarraclough 11mo ago
Some Blu-Rays have major spoilers in their menu animations, and some have unskippable ads, some of which may contain major spoilers. [0] It's also a criminal offence to create a backup, thanks to the DMCA. On the plus side, all UHD Blu
83.
by MaxBarraclough 11mo ago
Inventing a Star Trek-style teleporter would be quite something, but I don't see how it would advance the philosophy in any way. We already know the teleportation subjects would report 'feeling just the same' as before. If th
84.
by MaxBarraclough 11mo ago
Assuming you use Qt Widgets. As far as I can tell, Qt Quick doesn't have anything like the same set of polished widgets that integrate nicely into the target platform. It's been this way for years, they just don't seem intere
85.
by MaxBarraclough 11mo ago
> Surely you can see that an inner implementation of the icon class requiring a special hidden order In practice, programmers don't find it easy to keep in mind that certain functions might throw. This is a real problem with uncheck
86.
by MaxBarraclough 11mo ago
> don't have to write code for that exceptional behavior, except where it makes sense to. The great Raymond Chen wrote an excellent blog post on how this isn't really true, and how exceptions can lure programmers into mistakenl
87.
by MaxBarraclough 11mo ago
Agreed. In Java land, if I understand correctly the OpenJ9 JVM can (or at least could) beat HotSpot in memory consumption, while being slightly behind in execution times. It still sees only limited adoption. This may be just because it&#x27
88.
by MaxBarraclough 11mo ago
> nobody else besides the manufacturer could write the drivers for it to extract the most performance out of it Let's not go too far here. Reverse engineering and independent development of usable drivers are not impossible, they&#x
89.
by MaxBarraclough 11mo ago
> I was a big fan of a good keyboard-driven git TUI like magit, neogit, lazygit, etc... (as long as you learn the CLI first and understand it). How about tig ?
90.
by MaxBarraclough 11mo ago
ziml77's point is about the behaviour of the C# language. You seem to be talking about implementation concerns. They're not relevant.

More ›