261–270 of 364 posts
I think the weirdest way is using React. I mean, it feels so unnatural for me, compared to the jQuery way. You have to download thousands of packages, keep track of various dependencies and their security holes, adding an overhead for auditing them. HTML5 with jQuery IMHO still beats everything in simplicity and getting work done fastly
Noone is bashing Angular, whew!
Earlier quoted context omitted.
Why would I choose server side rendering? If I build the site in vue with the most optimized output settings, append hashes to files for perfect caching, drop the files in an S3 bucket, throw a CloudFront CDN on top of it with gzip compression, and build the front end of my backend as a REST api sitting in a lambda function that serves HTTPS requests, I never have to worry about server costs being more than pennies a…
Am I the only one to whom this description sounds like some version of hell?
Earlier quoted context omitted.
We target IE11 with angular1.6, React and Vue and it all runs very fast. The only time we ever had trouble were lists over a few hundred items long that our internal customers didn’t want paginated. But delivering those more demanding apps in react and vue solves all our IE11 is slow problems. On any other brothers the code might as well be native.
> lists over a few hundred items long that our internal customers didn’t want paginated. Does it not bother you that a machine that can do at least a billion computations in a second struggles with a list that short?
Earlier quoted context omitted.
Notes was a double-edged sword. It could be as terrible as you've heard, but on the other had it also let non-programmers build surprisingly useful applications all by themselves. (Which is part of why it stuck around for so long -- being useful, those apps tended to get wedged into critical parts of the business process, which meant you couldn't just pull them out and throw them away.)
Notes was conceived in 1984 and at the time was an amazing platform which featured a secure client/server architecture, RSA encryption, data replication and offline support. Both the Notes client and the server (later renamed to Domino) needed to run on multiple platforms (Win 3.x, OS/2, Netware, NT, Alpha, RISC systems etc), and while the code was native C code on each platform, all UI of the client was implemented…
https://motherfuckingwebsite.com/
Earlier quoted context omitted.
We target IE11 with angular1.6, React and Vue and it all runs very fast. The only time we ever had trouble were lists over a few hundred items long that our internal customers didn’t want paginated. But delivering those more demanding apps in react and vue solves all our IE11 is slow problems. On any other brothers the code might as well be native.
Wait why are you using all three of AngularJS, React, and Vue?
I wanted to move to React initially but after adding a single new app my boss hated the syntax and we switched to Vue. Vue is good too.
I think the weirdest way is using React. I mean, it feels so unnatural for me, compared to the jQuery way. You have to download thousands of packages, keep track of various dependencies and their security holes, adding an overhead for auditing them. HTML5 with jQuery IMHO still beats everything in simplicity and getting work done fastly
Here's the perfect React replacement for you: https://github.com/wisercoder/uibuilder It is a 200-line library, and you get React's templating technology, which is the best part of React. You can use jQuery for updating the screen.
Earlier quoted context omitted.
We target IE11 with angular1.6, React and Vue and it all runs very fast. The only time we ever had trouble were lists over a few hundred items long that our internal customers didn’t want paginated. But delivering those more demanding apps in react and vue solves all our IE11 is slow problems. On any other brothers the code might as well be native.
That would indeed be impressive, IE surely needs a ton of polyfills?
Earlier quoted context omitted.
If you generate a typical react app with create-react-app, you get ~1000 dependencies in node_modules: `npx create-react-app some-app-name --typescript` (it was actually exactly 1000 dependencies which is freaking me out because the number was so round. wondering if it am counting lines wrong `ls | wc -l`)
And 997 of those are development tooling dependencies that are not included in the application that you eventually deploy. Don't get me wrong, I would rather there were fewer development dependencies too, but they are tooling abstractions that you are _opting-in_ to. If that is still a cognitive burden, then there's nothing to stop you using React a build step through a CDN.
This website uses scatterplots instead of lists to display products: https://www.productchart.com So on Product Chart, you can for example say "Show me 300 smartphones and put the price on the x-axis and the size on the y-axis". It's a bit like you would lay out things on a table and then organize them by some criteria.
Looks really nice! Wouldn't a simple table be a better option in this case though? I quickly got tired hovering over each icon (very small icons too) to look at the specs. Looks very nice though.
This just makes me waste my time compared to a table where I can sort/filter by different criteria.
Most of the time, "creative" visualizations tend to actually obscure meaning, or worse, mislead viewers.
Recommended reading: Show me the numbers by Stephen Few (his blog is also great: http://www.perceptualedge.com/blog/)