Hacker Newsnew | past | comments | ask | show | jobs | submit | mrcino's commentslogin

The UI/UX design is not about standards and guidelines but about what the manager currently likes. There is no discipline because senior managers don't care until Excel cells turn red.

Steve Jobs was forcing design discipline across Apple products with furious determination because he actually cared.

That's how it ends, everything becomes an unmanageable, constantly changing mess because every manager likes something else and big firms are rotating their personnel every 3 years.

Because the above products of the same company are losing cohesion and consistency even if they are in the same product line which results in bad UX.

Design departments are not disciplined enough...


The Mythical Man-Month calls for a single person to be responsible for the design of a system. Steve Jobs was that guy for Apple. But once he left, there was no one strong enough to define the system across the whole company.

So, this is the AI Slop generator for the AI SlipSlop that Altman has announced lately.

Brave new internet, where humans are not needed for any "social" media anymore, AI will generate slop for bots without any human interaction in an endless cycle.


By Public knowledge sharing, do they mean bazillions of StackOverflow duplicates?


The article mentions that all kinds of posts were reduced, not just duplicates or even simple questions.


So much boilerplate and unnecessary keywords...

Frontends do not need boilerplate, they need a simple, efficient and maintainable way of interacting with data and managing mutations.


The Applescript/Hypercard script this is inspired by were created to resemble prose to make it easier to understand for non-technical people (and one can argue in hindsight that to be a misguided design goal)

There is no need for a light JS replacement to be as verbose as prose. The Venn diagram of engineers trying Hyperscript out on their side projects and people unfamiliar with code syntax are two distinct circles.

If you want to put logic in HTML attributes, it needs to be concise and expressive, not resembling English prose. Even APL would be a better choice.


> APL would be a better choice

I once had a Venn diagram to display the set of people who are fluent in APL-like languages but it was so small I needed a microscope to see it. Now I've no idea where it might be, I'm afraid I accidentally brushed it from the table along with some breadcrumbs


Hyperscript is designed to be easy to read when embedded within html. The xtalk[1] syntax is more verbose and stands out. This is intentional and is made up for, to an extent, by more expressive features like relative position expressions, CSS literals and so on:

  on click toggle .active on the next <div/>

Certainly not for everyone but it is being used in production in multiple applications.

1 - https://en.m.wikipedia.org/wiki/HyperTalk


If anything, this would allow you to omit a bunch of boilerplate that you'd otherwise need to do the same thing in React. (Example here: https://www.infoworld.com/article/3708109/intro-to-hyperscri...)


I do agree but am open to the idea that HyperTalk and COBOL are actually more understandable to masses of people who I don't relate to in really any way.

I see a visual language Node-RED with tunable parameters in nodes as the way but have kept up with this project a little... no reason user scripts need to be one or the other.

I guess developers will be valuable in implementing and supporting users in any case, I see these tools as reducing support and maintenance for doing variations from the day to day business use more than replacing the dev team.


It’s based on AppleScript so I think that’s by design.


Just use CLJS with Reagent, we had memoization out of the box for a couple of years...


I've heard great things about ClojureScript. My only problem is I don't want to have to touch the JVM.


Is it backward compatible?


With what? 8.2? 7.0? 5.4?

you're going to get a mix of yes and no depending on what you're trying to do. lots of things have been deprecated over the years.


Almost. Please read the section named "Deprecations and backward compatibility breaks" at the bottom of the post.


Yes


Brace yourself, DDoS is coming...


Jesus Christ, another version?

Let people learn previous features as having a feeling that your framework is constantly delivering new stuff and that you need to constantly catch up with them is increasing FOMO and is making people unsecure...


Would you have made the same comment if they went by minor versions instead, and this was v1.16.0?


Honestly, except maybe for the phasing out of Ivy, updating angular tend to be a non-issue.

(And yes, also the shitstorm that was AngularJS to Angular (4+), but that was a long time ago now.)


Just as with every AI tool you need to be an expert in scope that you are operating the AI tool...

You have to know reg-ex really well to use this tool safely.


Generate repetitive, default not interesting UIs and get stuck in prompt hell where being specific takes more time than actual designing and implementing with UI framework.

Ai revolution looks more and more like WYSIWYG editors hype long time ago. Every manager thinks that he will be able to do everything on their own with AI but it will end with creating jobs like Senior AI Prompt Developer...


As if the site we're currently using is on the cutting edge of design. If there's utility there's value.


While I tend to agree, I’m also somewhat hopeful it can be a force multiplier for myself. I don’t think it will actually replace designers, anymore than WYSIWYG editors/Squarespace/Wix et al did. But it might make some design processes quicker for those who are already skilled, and that would be pretty neat.


Reminds me of all that hype around Business Process Management (BPM) and we ended up with "Integration Specialists" to actually build the process flows because the fancy diagram builders only went so far.


This is useful for probably the lower 20% difficulty of UI work. And I bet that developers will get (over)loaded with the responsibility of writing prompts instead of a new job being created.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: