

Use the IoT LTSC version and install it using Rufus. Zero bloat, very fast, no clunk.
Use the IoT LTSC version and install it using Rufus. Zero bloat, very fast, no clunk.
Green is good and red is bad. If that wasn’t the intent they should have used different colours.
Sure, but without further context, “frontend” means the web. And “frontend language” means languages that were designed for the frontend. You can write a website fromtend in Python, but you absolutely shouldn’t!
You can use languages like Java and Rust too which are more reasonable options, but they aren’t “frontend languages”.
Interesting, but the colours for exceptions are inverted. One of the features that Elm touts on its front page is that it doesn’t have exceptions.
Structural equality is also debatable.
That’s nitpicking. It is statically typed. Is Dart not statically typed because it has dynamic
.
You could call it “gradually typed” if you want to be pedantic.
can be circumvented pretty easily
That means it isn’t sound.
Languages well suited for client side web code. Most of these (maybe all?) compile to JavaScript and are designed for the web.
Oh you mean when I said this?
I expect it helps people of all experience levels fairly equally, but only with tasks that are relatively simple.
No I don’t have actual data, just direct personal experience of asking AI to do simple and complex tasks - it does much better on simple tasks, especially in very widely discussed domains (HTML, CSS, JavaScript, Python etc.) Ask it any SystemVerilog stuff and it gets it wrong almost every time annoyingly!
What do you mean? I’ve seen people say that all the time on HN. No I’m not going to go and search for comments.
Yeah there are pros and cons. Desktop apps are not sandboxed. Mobile apps are often missing features and are annoying to install. Websites often have poor performance or janky UX on mobile, and you need to be online, and you don’t have control of their availability.
I think the best option depends on what the thing is - ordering food from a random pub? Web site. Video editing? App.
Proper reasoning is always needed if you want a guarantee.
You formally verify your regexes? Doubtful.
Does that imply anything at all in LLMs’ favour?
Yes it suggest lower cognitive load.
Great, but I wouldn’t be shouting from the rooftops how Wayland has created a better experience for users just yet.
Ok I can see you haven’t actually come across any complex regexes yet…
(Which is probably a good thing tbh - if you’re writing complex regexes you’re doing it wrong.)
I work in RISC-V CPU development and I’d say 5-10 years is about right for when we’ll see usable RISC-V desktop class machines.
There isn’t really any RVA22 hardware you’d really want to run a desktop on anyway, so it’s a very logical decision. RVA23 is a much more sensible base - it requires Vector and Hypervisor.
This is stupid pedantry. By that logic literally nothing is complex because everything is made up of simple parts.
Damn there are so many AI critics who have clearly not seriously tried it. It’s like the smartphone naysayers of 2007 but much much worse.
You don’t have to. You can read it.
Regexes aren’t hard to write, their logic is quite simple.
He did say complex regex. A complex regex is not simple.
I think the combination of two things actually makes this slightly difficult to defeat:
There are a few ways I can think of to circumvent it:
Write an app that displays a video and simultaneously averages the colour of the front facing camera and applies that as a filter to the video, emulating a reflective display. There would be some lag but I bet it works.
Use the Android emulator and directly read the screen colour, and use that to filter the camera input (and connect the camera to an AI video). I dunno how detectable the Android emulator is these days though. Probably the age verification apps can detect it fairly easily.
Find a homeless person and pay them £2 to look at your phone.