There's a big overlap. Recent research shows that 80% of people on the autism spectrum also have adhd, and 50% of people with adhd also are on the autism spectrum.
and do you find powershell to be a simpler alternative? i recently had to look into a 100 or so lines powershell script and it felt crazily hard to read. Good thing I had access to the guy who wrote it so that he just told me what it was supposed to do (he gave up explaining the script)
Yes the powershell language itself is a poorly thought-out hack but using shell scripting for non-trivial tasks is a related but different problem that has to do more with a (thankfully narrowing !) skillset gap between devops/IT people and software developers. So just like a 100 or so line bash script would probably be better off written in python so would a 100 line PS script be better done in any .NET language and exposed as a cmdlet
In the unix-compatible world, you could take a look at openbsd as an example of OS that is not growing exponentially. Yet, the web browsers are the same two beasts that you find elsewhere in linuxes.
For a more radical approach to what you ask, look at plan9. There are some modern forks that run on modern hardware.
I recently used html5 sumary/detail to implement a treeview and it was the best experience ever solving such problem on the web. Very simple and easily customizable via css, and if you render it on the server, you don't need javascript at all.
Unfortunately I didn't find an example that was simple enough on the web, and the work I did is not open source, so here is the best link I found, which was by the way what I used to derive my implementation:
Unfortunately, this is missing the semantic metadata about the fact that it's a tree. It might be fine in some cases, but in general you would want to add some Aria attributes. But i'm not sure whether you could generate the entire thing server-side.
Here's some examples of this lovely element. I can't believe I hadn't heard about this before! I shared it with several web designers/developer friends who all had the same reaction.
if parts of the web browser start being shipped as wasm code, we will eventually reach the point where the web browser shipped to the user is only a wasm vm, and all the rest will be shipped as optional libraries or even downloaded on the fly. Even stuff like the html engine, the css, and the javascript. In that world, using the messy web standards evolved over time would be optional. The web browser would then become the universal virtual machine that the world seems to want it to be, instead of a browser. The web would be the app distribution system. One could for example, decide to write their site using tcl/tk.
Implementing the wasm vm and its basic apis would be simpler in a new operating system. Because the way it is now, the web browser itself is more complex that writing a simple operating system. That hinders innovation in the Operating System space.
There's a HUGE way to go to get there and I don't believe we really ever will. OSes support every language, 100s of Input Method Editors, all the issues of left to right and more complex text rendering than English. Asking every webpage to provide all of that and to keep all of that up-to-date would be a huge loss for the web and app dev in general.
> Consequently, there are now around 40 high-level programming languages that support WebAssembly, including C and C++, Python, Go, Rust, Java, and PHP. Wasm is not a new language, but a portable, pre-compiled, cross-platform binary instruction set for a virtual machine that runs in the browser.
All I can see is people wanting to use web-technologies to develop applications. So I would place my bet on the DOM/CSS evolving further and swallowing everything. JavaScript might get some contenders.
Good point. That should probably be the case for the majority of generation who entered the programming world in the last 20 years, which is quite a lot of people. But yet, old farts like me may disagree.
> One could for example, decide to write their site using tcl/tk.
Please, please don't do that. Tk is completely inaccessible to blind people via screen readers, and probably people with some other disabilities as well, on all platforms. Most toolkits written by people who decide to throw out those messy web standards would probably have the same problem.
Exactly my thoughts when I first read of WASI: conceptually you could now have a WASI runtime ("OS") and an HTML.wasm potentially independently developed and swappable.
And since WASI is a lot smaller surface, it is easier to audit, test, reimplement, etc.
In my experience, reality is unpredictable enough that no one actually know what the requirements will be two versions down the road. In practice you end up with code that is more complex than what the current problem needs, trying to solve a future need that you presume will happen but you don’t really know what it is and when it will happen.
stdlib was once an exemplar of good, idiomatic Go code, but a lot of the idioms it uses haven't withstood the test of time, and it's less and less appropriate as an example.
This is true, but it's still worth poking around for pre-existing solutions to problems. My editor will jump to stdlib definitions so I've learned a lot just diving into various stdlib packages (I remember the JSON parser being a good one).
Well, I don't work remotely but I am waiting on a task to be completed by another team for about a week now. It's something that can't possibly take more than one hour or so to be completed, and I even talked to them in person before submitting the task. That didn't change a thing about their deadlines.
