Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

UnsuckJS: Progressively enhance HTML with lightweight JavaScript libraries

unsuckjs.com

Post reply on HN
Print view View original

31–40 of 194 posts

Re: UnsuckJS: Progressively enhance HTML with lightweight JavaScript libraries

#32

Post by noizejoy »

adparadox wrote: post #11
canadiantim wrote: post #2

Looks great, love the list so thanks for putting it together. In an ideal world your table would also have a first commit row that way I can better compare how well established each library is (GitHub stars mostly does this but date of first commit would help give sense of momentum too)

I didn't post the site to HN, but I did create it. Adding the first commit is an interesting idea. Or some way to measure longevity (i.e. how long has the library been worked on). I'll try to figure out a good way to do that or if you put up a PR I will take a look at it: https://github.com/adamghill/unsuckjs.com .

Nice idea! I was just surprised to see the table rows and columns opposite of what I’m used to seeing in lists where one dimension is more likely to grow much longer than the other.

i.e. I would have expected the libraries as rows, rather than columns. More like such lists are typically done in Wikipedia.

Re: UnsuckJS: Progressively enhance HTML with lightweight JavaScript libraries

#33

Post by spankalee »

smusamashah wrote: post #23

There should be another row that which of these can be included as a standalone javascript lib in html instead of requiring NPM.

For Lit, you can use pre-bundled versions from a CDN: https://lit.dev/docs/getting-started/#use-bundles

Re: UnsuckJS: Progressively enhance HTML with lightweight JavaScript libraries

#34

Post by adparadox »

smusamashah wrote: post #23

There should be another row that which of these can be included as a standalone javascript lib in html instead of requiring NPM.

Not requiring NPM was one of my original requirements for anything on this list. All of these libraries should be available from HTML directly -- let me know or make a PR if that isn't the case.

Re: UnsuckJS: Progressively enhance HTML with lightweight JavaScript libraries

#35

Post by spankalee »

satvikpendem wrote: post #7

I can do the same thing via NextJS and output pure HTML and CSS without any JS at all. Or with server components, output only the minimal JS needed. Not sure why everyone wants to write a programming language inside HTML like lit does.

How is Lit's use of JS in templates any different than JSX? Both use JS for expressions and control-flow.

Re: UnsuckJS: Progressively enhance HTML with lightweight JavaScript libraries

#36

Post by spankalee »

FireInsight wrote: post #8

I get these for when your stack contains python/go/ruby and your page is SSR. But more recently I've just come to enjoy the full blown Javascript Framework. I use Svelte exclusively, and the bundle sizes aren't too large thanks to the compiler. I can write TS which is way more comfortable than JS or even Python or Go IMO.

You can get small sizes, great DX, first-class TypeScript support, all without the compiler though.

Re: UnsuckJS: Progressively enhance HTML with lightweight JavaScript libraries

#38

Post by adparadox »

noizejoy wrote: post #32
adparadox wrote: post #11

Earlier quoted context omitted.

I didn't post the site to HN, but I did create it. Adding the first commit is an interesting idea. Or some way to measure longevity (i.e. how long has the library been worked on). I'll try to figure out a good way to do that or if you put up a PR I will take a look at it: https://github.com/adamghill/unsuckjs.com .

Nice idea! I was just surprised to see the table rows and columns opposite of what I’m used to seeing in lists where one dimension is more likely to grow much longer than the other. i.e. I would have expected the libraries as rows, rather than columns. More like such lists are typically done in Wikipedia.

It definitely might make more sense that way! I was playing around with different ways to display the data and landed on this approach even though maybe it's a little clunky. I could flip it and see how it feels -- thanks for the suggestion!

Re: UnsuckJS: Progressively enhance HTML with lightweight JavaScript libraries

#39

Post by daveoc64 »

DaiPlusPlus wrote: post #18

The bottom row of the table is "IE11 Compatible". ...IE11 hasn't been relevant on the public-web for at least a decade now, and I'm fairly sure it's now entirely gone from corporate/enterprise situations now too, given MS' even-more-aggressive-than-usual campaign to kill it off in Feburary of this year: https://www.cnet.com/tech/services-and-software/rip-internet... ...why is that there? It's weird - it's like saying…

Internet Explorer 11 is still supported in Windows Server 2022, which goes out of support in October 2031. It's also supported in Server 2016 and 2019.

It's also supported in Windows 10 LTSC versions for large companies.

IE 11 mode for Edge is also supported until at least 2029 on all currently in-support Windows operating systems.

So it can be very relevant if you have legacy systems that still need to be maintained.

Post reply on HN