I feel old now. I'm fairly sure that we could do this almost as fast with VB or Delphi a couple of decades ago, but a little more deterministic results instead of having the tool inferring it from the label names. We had this and then we shoved everything in the browser and forgot that we could do this without using huge amount of compute of some generative AI model. Look at me I'm old yelling at clouds!
Honest question: what's the point of saying that something could be done 20 years ago (when most people weren't online or using a computer)?
20 years ago we also had music, pizza, movies, games and old people yelling at clouds.
I wonder if it makes sense to learn web development. When I am done in two years, how to find a job which is not already done by an AI? :-(
Its best to approach learning from a place of curiosity and never be 'done'.
However, as an answer to your question: If you're looking for a skill to learn once in a short time and apply that for a decade; then web front-end coding is among the worst options.
Hey, Steve here from tldraw. This is a toy project with a horrible security pattern, sorry. If you want to run it locally or check out the source, it's here: https://github.com/tldraw/draw-a-ui . You can also see a bunch of other examples at https://twitter.com/tldraw . Happy to answer any questions about tldraw/this project. It's definitely not putting anyone out of work, but it's a blast to play with. Here's a more…
Launch launch launch!
Seriously this is lightning in a bottle. Charge $5/mo and have users bring their own OpenAI key.
Here’s a freshly MIT’ed licensing server you can use. It’s written in elixir and powers https://go.robocoder.app
Such recent demos show both how impressively ML/AI has advanced recently, and how unimpressively repetitive and unoriginal tasks keep being reimplemented by millions of developers worldwide. Since most UI screens can be accurately described in one or two paragraphs, it's no wonder they can be represented in much detail in a relatively small embedding vector.
It just exposes how stupid our software stacks are. Everything is driven by "well, maybe they'd want to customize this and that and that and three hundred irrelevant details". When in reality all we ever wanted was to separate the functionality from its presentation. Which, incidentally, was exactly the Web we had in 1996 with just bare HTML. Things have gone horribly, horribly wrong in such a mind-bogglingly stupid way and nobody is better for it. Oh but those dropshadows and inner flexboxes or something.
> we spend a very small fraction of our time on building things that are unique to our business. I usually see this in places/cultures that value code-beautification projects rather than delivering value to the customer. Sometimes, they even want to do the latter, but actually do the former. If you work somewhere that focuses on delivering value, the devs constantly complain about technical debt that will never, ever…
"Code beautification" is not the point, but a tool. Smaller and clearer code could be faster to write, and harder to make mistakes using. This is why e.g. Rails can be so good at producing certain kinds of apps very quickly and in very few LOCs. The problem is, of course, that simplicity follows complexity, not the other way around. Because of that, it's mostly "trivial" and "repetitive" tasks that receive polished t…
Code Beautification is a waste of time and ossifies a code base. It's a form of optimization that actually makes the code harder to change and the business less agile. It is pretty though.
> we spend a very small fraction of our time on building things that are unique to our business. I usually see this in places/cultures that value code-beautification projects rather than delivering value to the customer. Sometimes, they even want to do the latter, but actually do the former. If you work somewhere that focuses on delivering value, the devs constantly complain about technical debt that will never, ever…
> somewhere that focuses on delivering value, the devs constantly complain about technical debt that will never, ever get fixed Value, or short-term value? When the codebase gets hard to manage, the value is there.
I generally try to steer any team I work on away from short-term value. It's an addictive drug to managers that eventually gets used up.
Hopefully this sounds like helpful feedback instead of annoying nitpicking: I found that the substantial "flash of unstyled content" when the page first loads to be very jarring/unappetizing. I think it would be worthwhile to investigate one of the approaches that can mitigate this FOUC effect. Cheers and good luck!!!
thanks for the feedback ! I cannot replicate that on my computer with any browser, and all seems normal to google pagespeed insights as well: https://pagespeed.web.dev/analysis/https-sql-ophir-dev/4o7q6... Which browser/device are you using, and from where ?
Disable the cache in dev-tools, you can't miss it.
I feel old now. I'm fairly sure that we could do this almost as fast with VB or Delphi a couple of decades ago, but a little more deterministic results instead of having the tool inferring it from the label names. We had this and then we shoved everything in the browser and forgot that we could do this without using huge amount of compute of some generative AI model. Look at me I'm old yelling at clouds!
You're absolutely correct. When we went to the browser we took 30 years of UI development knowledge and UI/UX principle and flushed it down the toilet. Only very recently have we started to gain composability in browser UIs through things like React, and it's a sad facsimile of the widget composability we had in WYSIWYG UI development on PCs in the late 1980s and early 1990s. The web is a shit UI platform, but that's…
The web is a much better UI platform than what's available in linux desktop and whatever took 30 years of UX development in Linux wasn't flushed down the toilet (emacs, vi, GNU, ...). MS Windows users miss their Delphi/VB software.
Such recent demos show both how impressively ML/AI has advanced recently, and how unimpressively repetitive and unoriginal tasks keep being reimplemented by millions of developers worldwide. Since most UI screens can be accurately described in one or two paragraphs, it's no wonder they can be represented in much detail in a relatively small embedding vector.
In that vein, I wonder if you use these embeddings and compression to work out a new sort of programming language which could extremely concisely represent these concepts. Probably the actual result would be so complex as to be worthless, like code golf languages but worse, but maybe it could help us come up with an interesting new programming language paradigm.
I gave it a mockup from a FB interview question (two lists of checkboxes with two buttons to swap checked items between them) and it nailed it: https://gist.github.com/milesrichardson/2a2f77d4bfb19c3b28dc...
I checked in a screen reader. Nothing is announced when pressing the buttons. This is a problem. It should say something like “Checkbox B moved to the left”. Without any sort of announcement, the user has no idea if pressing the button did anything. Test page: https://output.jsbin.com/jixoqur/quiet