81–90 of 108 posts
Needing an ajax request to paginate a table seems like a big step backwards from modern web applications.
How is this different from Vaadin (other than the language, of course)? https://vaadin.com/
Would also like to know major differences to Anvil?
Anvil also emphasises their dev tools, it’s quite an integrated environment, between IDE, data, and deployments.
Needing an ajax request to paginate a table seems like a big step backwards from modern web applications.
Am I missing something? Pagination would surely require a request, unless you’re loading the full data set into the client up front, which would be a bad idea in many use cases?
I feel bad about projects like these, I really do. I'm sure a lot of effort have been put in and it probably satisfies what OP wants to do. But in the end, no one serious would ever consider using it.
Maybe not.
Would anyone use this for “line of business” applications? Internal tools? The signed-in experience on an enterprisey product?
Most definitely.
Guess which one 90% of software falls into.
I work at a tech company, we sell to consumers, we’d never use this for customer facing stuff, but being able to rapidly build web apps that show tabular data and editing controls with various integrations with our services for internal customers and partners is critical. If we built that as fancy React apps all the time we’d never get anywhere.
Be careful. This is licensed under the AGPL, which basically makes it unusable. Or a commercial license can be purchased.
I feel bad about projects like these, I really do. I'm sure a lot of effort have been put in and it probably satisfies what OP wants to do. But in the end, no one serious would ever consider using it.
You'd be surprised. Many highly successful websites and services use non-mainstream projects.
Besides that trite observation could have been said for any project (even the most successful ones like Rails) when they first started.
Earlier quoted context omitted.
Transpiling to JavaScript is a bug on the web, not a feature. node and npm is a shit show. Having to deal with it a couple days ago. I wish that entire ecosystem would just die. I can make a sophisticated python web app with 20 packages. Or in JavaScript I'll need a few hundred that have massive vulnerabilities and conflicts. Hell npm reported the most modern packages I was installing had over 200 vulnerabilities. Ja…
Amen brother. It just baffles me that most people here in HN enjoy working with JavaScript and its derivatives. I feel bad for them, like when you see a 14 year old kid smoking and drinking
Be careful. This is licensed under the AGPL, which basically makes it unusable. Or a commercial license can be purchased.
So, the same way Adobe Photoshop is "unusable" or Oracle DB?
Earlier quoted context omitted.
>But in the end, no one serious would ever consider using it. Why not? I would say it is the other way around. For any web application project of decent size there is almost always a transpilation step that converts whatever programming language your source code is in, into JavaScript (usually ES5). We also had very successful and widely used projects like GWT for years (GWT was first released in 2006!!!).
Transpiling to JavaScript is a bug on the web, not a feature. node and npm is a shit show. Having to deal with it a couple days ago. I wish that entire ecosystem would just die. I can make a sophisticated python web app with 20 packages. Or in JavaScript I'll need a few hundred that have massive vulnerabilities and conflicts. Hell npm reported the most modern packages I was installing had over 200 vulnerabilities. Ja…
"I had a bad experience (being unexperienced and only delving into that ecosystem a couple days ago) so it's bad"
Earlier quoted context omitted.
I think this is a symptom of being accessible not the language or its tools. NPM is fantastic and anytime I use Go or anything like that I miss it sorely. Even javascript itself isn't "bad". There are ugly parts but anything written in the modern spec is basically semantically the same as any other language like python. The problem is that people writing packages on the backend are bootcamp grads, frontend devs, and…
I don't think it is possible to separate language from tools or community. Those things are always together. It is entirely possible that Javascript itself is an OK language, but it is too late now. The community has already decided that packages should be tiny, that changing prototype of "array" object is an acceptable thing to do, that failing fast is bad and the best reaction to errors is to mess up the page layou…
I don't think so, you can always just use the language in your own style and cherry-pick any tools that align with it.
Like e.g. the Play framework ignored the main standards and idioms of Java development in its day.
Or how every game studio just uses its own version of C++ and forbids tons of features.