You can't really occupy useful land without expecting quick and dire consequences.
37,790 karma · joined September 7, 2019
You can't really occupy useful land without expecting quick and dire consequences.
- https://github.com/canonical/dqlite
Plenty of consumer products does just this? Raspberry PI basically spawned an entire industry around this very idea. Bunch of analog musical instruments does the same, some even come with signal graphs and such to teach you the insides of the instrument.
Not even Apple can get it correct it seems, as in CarPlay, if there is a incoming call, it covers the entire screen with the person/info who is calling, so if you're using navigation, until you either reject the call or pick up, it hides the maps behind the notification...
> Like every other framework, we've come to the realisation that Knockout was right all along.
> Svelte 5's reactivity is powered by signals, which are essentially what Knockout was doing in 2010. More recently, signals have been popularised by Solid and adopted by a multitude of other frameworks.
> We're doing things a bit differently though. In Svelte 5, signals are an under-the-hood implementation detail rather than something you interact with directly.
That's a sad development and further makes the framework more complect (as defined by Rich Hickey), with more hidden layers and "magic".
How many of those have a clear vertical space reaching to the sky?
Most balconies around me in a European capital have other balconies above them, all up to the roof, which would be the only suitable place for a drone to land. No fire escapes at 99% of the buildings here.
I don't see anything mentioned about this, nor other similar issues, either on the website or in the GitHub repository.
Are you offering some functionality that help people manage this, or how do you suggest people approach this "when not if" problem?
How much money were they given to start? I looked around for the numbers but I couldn't find it, but seems you were able to, could you share the full number you found?
Simple, tell me what changes, where I can read more and that's it. It's the perfect release notes.
But, as always, people like different things, as is apparent here :)
Seems to be a personal website though, so some leeway should be given, although I also found it a bit annoying. Especially the part when you go beyond the article contents and gets sent to the "homepage", but scrolling back doesn't go back to the article contents anymore.
https://www.techempower.com/benchmarks/#section=data-r21&tes...
Sure, Rust and C++ is probably faster when used naively, but I'm sure you'd have a harder time develop stuff in those languages.
Personally I'd probably reach for Rust before touching Java with a ten-foot pole, but people have different preferences for how easy a language should be to pick up, and if you're used to OOP and C-like languages, Java is pretty easy to pick up.
> Long l1 = Long.parseUnsignedLong("17916881237904312345");
Or, just use BigInteger
> trading off a small amount of convenience to gain a large amount of safety
Each feature links to a deeper dive into it.
C# $"{x} plus {y} equals {x + y}"
Visual Basic $"{x} plus {y} equals {x + y}"
Python f"{x} plus {y} equals {x + y}"
Scala s"$x plus $y equals ${x + y}"
Groovy "$x plus $y equals ${x + y}"
Kotlin "$x plus $y equals ${x + y}"
JavaScript `${x} plus ${y} equals ${x + y}`
Ruby "#{x} plus #{y} equals #{x + y}"
Swift "\(x) plus \(y) equals \(x + y)"
Is any of those actually better? You have a non-existing better suggestion that works in the same cases they outline in the JEP?I think the following is the main part to keep in mind:
> For Java, we would like to have a string composition feature that achieves the clarity of interpolation but achieves a safer result out-of-the-box, perhaps trading off a small amount of convenience to gain a large amount of safety.
One huge problem with no/low code solutions is that people usually think that this doesn't need to be done for no/low code solutions, only for code solutions. But solutions using nodes in order to build stuff also need to be revisited, refactored and thought of as abstractions.
Might be, but they really dragged their feet using it for their phones instead of Lightning, and I think I remember Apple saying they couldn't use USB-C and have the phones remain as thin as they wanted them.
But, as soon as regulation appeared that they have to, suddenly it became possible.
> OpenDocument - Initial release: 1 May 2005; 18 years ago
> SQLite - Initial release: 17 August 2000; 23 years ago
Wonder what gives.