progx

10 ms·

121.
by progx 3y ago
Yes, the update politics of ember is a good example for all. But it comes normally with a cost (features, speed, better solutions, whatever.... don't know currently enough about ember to form a judgment there). I used ember too for a l
122.
by progx 3y ago
And now from client side rendering (CSR) back to server side rendering (SSR). The thing, that we done 20 years ago, but now only more complicated, with more tools, more setups, etc.
123.
by progx 3y ago
The problem in the past was primary browser incompatibility. That was why jQuery exists and was so successfull. Different render output with different css settings was an other problem. But, thank god, since IE dies, this problems are solve
124.
by progx 3y ago
And how many times you have to update your app? How many time you need for maintain?
125.
by progx 3y ago
Starting a fresh new (internal) project in our company, no specs, no borders, we can use any JS lib, framework, tool, whatever. Now we stay like a kid in front of a candy shop and don't know what to choose. Anything has pros and cons,
126.
by progx 3y ago
Not only our trains!
127.
by progx 3y ago
Keep up-to-date could be a job for an AI. You wrote your documentation for a specific version. The AI could know detect code change and if it affects the documentation. Not 100%, but it could help to find the outdated docs. In huge projects
128.
by progx 3y ago
That is why we now step back to SSR-apps. No api necessary, no extra layers, no extra bloat and it is fast and scalable enough for the most apps.
129.
by progx 3y ago
But you have to look at the whole string and check if send has a further parameter. With `send(msg)` you see it without taking extra time of reading. And let the compiler optimize your code, that is the job of a compiler. Write your code fo
130.
by progx 3y ago
In this case the variable is the documentation of the code. You don't have to write something like "this is the message", you can see it.
131.
by progx 3y ago
Its all a problem of formatting, for me this is simple to read. const { status } = await send( capitalize(greeting) + "!" ) But i would not concat things in a method call, bad style. const message =
132.
by progx 3y ago
The difference between him and you: he has expertise.
133.
by progx 3y ago
I do this since ~20 years with a simple Calc-Table. Easy overview and simple to search.
134.
by progx 3y ago
10x less code is impossible. Either it adds much hidden magic code or it pumps the other language examples, or it lacks on functionality. Nue is small, so it adds no hidden magic. Some examples are really huge.
135.
by progx 3y ago
Look at the millions of free to play games in the App-Stores. Normally you have 98% of free playing users paying nothing, 2% pay. Imagine now you have 1 million installs. 2% (20.000) pay you 200.000 / year. 980.000 players pay nothing.
136.
by progx 3y ago
That is true, the first thing i ask myself when i read "Frontend Troublesolver - Nue is a powerful React, Vue, Next.js, Vite, and Astro alternative. It might change the way you develop for the web forever." ... was, how? And then
137.
by progx 3y ago
The problem in the past with css was the inconsistent browser implementation, this should be solved since some years. And now we have native nesting, wich was in old times a reason for use things like sass/scss/... CSS-Variables t
138.
by progx 3y ago
I know CSS and have to look always into the Tailwind documentation to find the corresponding settings. As long as you use tailwind 0815 settings everything is ok, but not easier as css (if you know css).
139.
by progx 3y ago
You get customer when you solve a real problem for them. CI-Systems exists, slow or fast doesn't be a problem for most of the devs, cause you run normally everything local and only on publish in a remote CI-system. So CI-Systems exists
140.
by progx 3y ago
It should be implemented on os-system level, so you can access the content, no matter with which app.
141.
by progx 3y ago
Need is the wrong word, sometimes it is necessary. Look at npm, long time they not include new features and made less progress. That time yarn was born. pnpm and other followed, cause npm did not have features, security solutions, and other
142.
by progx 3y ago
And you write this crap `class="my-4 mb-sm-5 mb-lg-6"`hundreds of times in complex applications or `class="foo"`?
143.
by progx 3y ago
Which things? Individual styled simple elements? Sure. Complex reusable and customizeable components, no way.
144.
by progx 3y ago
That is the point: which kind of projects? You all fight, but nobody says what exactly they develop. A webpage and Tailwind is absolutely fun. An app with reusable complex components, Tailwind is a pain. Themes, dynamic tailwind is a pain,
145.
by progx 3y ago
I disagree, tried it with a small custom component lib in our company. It was a huge overhead to add options for e.g. a button-component. You can use Tailwind on top level and it is easy. But as soon as you have complex components with sub-
146.
by progx 3y ago
And when you create an App with hundreds of buttons? And when the designer change his mind and border-red should not be used anymore? And what if you have small changes, e.g. ``` <button class="bg-blue-500 hover:bg-blue-700 text-whi
147.
by progx 3y ago
1. For component usage and in this case only restricted. You can only style the top layer of a component, not each part. But for component development, tailwind made it complex, e.g. if you want to make it possible to set / add custom
148.
by progx 3y ago
Wordpress, React, many others win too and nobody would say, that these are superior to anything else. Like in WordPress or React you can fiddle with Tailwind too. People like to fiddle. You can make things easy, or fiddle, what did people d
149.
by progx 3y ago
Main thing to distinguish: small team / big team and or small app / huge app. For small teams frameworks like react & others are (sometimes, not always) overbloated and overkill. If you want to use finished components without
150.
by progx 3y ago
Services, that solve a problem, did not need SEO.

More ›