kaba0

12 ms·

121.
by kaba0 2y ago
Screen sharing has been working fine for years now. Chromium-based browsers and firefox all “just works”, that is every electron-based app as well. Sometimes the latter may use a too old version of electron, but it’s just a website either w
122.
by kaba0 2y ago
Are they even doing a release build?
123.
by kaba0 2y ago
I do like sketching those up, but in an ultra-simplistic way (literally just a word/label and some arrows). Paper sort of extends my working memory, so I use it as a temporary storage to think through something that’s getting too big t
124.
by kaba0 2y ago
There is no universally correct layouting. I for one absolutely detest epub versions of scientific books. Even if they are the official variant and not a generated one from some other format that understandably sucks, diagrams will be all a
125.
by kaba0 2y ago
I found this post absolutely fascinating! I got thinking, is there a Turing-complete simple abstraction that is differentiable, without approximation? I have heard about Neural Turing machines (but only as a layman), but from a quick peek
126.
by kaba0 2y ago
Well, it has compiler intrinsics for unsigned numbers, for what it’s worth.
127.
by kaba0 2y ago
Seems like a trivial thing to fix though, it was a lack of will over an explicit design tradeoff. At Applet’s time there was simply no such API surface to attach to and make useful programs.
128.
by kaba0 2y ago
Web pages at the time could at most <blink>, its interactivity was extremely limited compared to what we have know. Meanwhile a java applet could include a full-blown IDE/CAD/what have you
129.
by kaba0 2y ago
You can’t just compare across decades of software and hardware development. Even downloading native binaries would have been sluggish, as the download would have been slow with those download speeds.
130.
by kaba0 2y ago
Wasm is more open, because we effectively have 1.5 browsers left, and whatever google decides will be the de facto “web standard” everyone should follow. If google were pushing for a slightly revamped jvm/applet model, that would be th
131.
by kaba0 2y ago
Are they validating code to the same degree though? Like, there are obviously learned lessons in how WASM is designed, but at the same time JVM byte code being at a slightly higher level of abstraction can outright make certain incorrect co
132.
by kaba0 2y ago
Funnily enough, wasm also has the problem of “slow to load”. In that vein, a higher level bytecode would probably result in smaller files to transport. And before someone adds, the JVM also supports loading stuff in a streaming way - one ju
133.
by kaba0 2y ago
> I think the first approach gives a lot more room for the host to create optimizations, to the point we could see hardware with custom instructions to make WASM faster Heh, there were literally CPUs with some support for the JVM! But it
134.
by kaba0 2y ago
I would add that most of it was politics. The JVM is not fundamentally insecure the same say as neither is any Turing-complete abstraction like an x86 emulator or so. It’s always the attached APIs that open up new attack surfaces. Since the
135.
by kaba0 2y ago
No companies (at least above the “tiny” category) care about anything, they are paper-clip machines and the only thing preventing them from extracting iron from our blood is the law.
136.
by kaba0 2y ago
A better metric for whether you think about it or not would be at refactor time . In Java, you can just move something around in any way or shape, change its lifetime semantics very liberally (e.g. make it have a single instance, or make e
137.
by kaba0 2y ago
Types [1] can only reason about categories of values, not about values. Tests and types do have an overlap, but the best option is both. Especially when combined with fuzzing, types can exclude large number of cases, making it even more e
138.
by kaba0 2y ago
You can hardly get higher quality code than what is generally available in Java, especially with their stability. Wrapping it to use the language conventions seems like a pretty solid choice to me. The dev xp, I sorta agree on, but it has i
139.
by kaba0 2y ago
For the majority of executing code, there is no fundamental difference when it comes to a JIT compiler. Besides, GraalVM can produce a native executable for pretty much any JVM language/program.
140.
by kaba0 2y ago
Scala 3? It has the vast Java ecosystem available and state of the art GCs (plural), with either a focus on throughput or low-latency. Also, it can exclude the null value from the type system, marking it explicitly with a union type.
141.
by kaba0 2y ago
Go is only modern in release date.
142.
by kaba0 2y ago
> but this is like judging Android by the cheapest phone I can buy, which is also agonizingly slow Nope, even running android on the same pinephone hardware results in a smooth system - it’s almost like google has been spending dollar bi
143.
by kaba0 2y ago
How are intents not scriptable? I have an app that can literally call any other intent, but I can even write a bash/python script and run it from Termux to execute whatever I want. Look up the `am` executable. Re the “killing stuff” pa
144.
by kaba0 2y ago
> I suspect you would find Android on that hardware to also suck Not at all, android is smooth as butter on even significantly worse hardware. > if you must download random untrusted code and execute it, then you should run it inside
145.
by kaba0 2y ago
Who would that benefit? Like, they have to service these devices, a cable connection is just much more reliable.
146.
by kaba0 2y ago
They have a proper, standard , high-level way of interacting with each other, literally the whole OS is built around than. Read up on android services, intents, etc. It is eons better than dbus-ing and writing to random files all over my
147.
by kaba0 2y ago
I didn’t mean to “shit” on the project, I did buy it as a means to both support it and to toy around with it - and yeah, the “free hardware” (which is arguably a bit naive and marketing-y goal) definitely doesn’t help create a device fit fo
148.
by kaba0 2y ago
Just the lack of.. the whole ecosystem adopting the restricted model and there being a properly specified and documented model in the first place.
149.
by kaba0 2y ago
> Just without open-source drivers for some freakish reason Because manufacturers buy random parts from other suppliers, who may or may not own the source code, and they often legally simply can’t share forward that code.
150.
by kaba0 2y ago
In what way is it “an unusable toy”?

More ›