407 karma · joined December 15, 2016
javascript:(function()%7Bfor(u%20of%20document.querySelectorAll('.hnuser'))for(u.prepend(c%3Ddocument.createElement('canvas'))%2Cx%3Dc.getContext('2d')%2Cc.width%3D18%2Cc.height%3D14%2Cc.style.imageRendering%3D%22pixelated%22%2Cs%3Du.innerText%2Cr%3D1%2Ci%3D28%2Bs.length%3Bi--%3Bi%3C28%3Fr%3E%3E%3E29%3EXX%2F3%2BY%2F2%26%26x.fillRect(6%2B2X%2C2Y%2C2%2C2)%26x.fillRect(6-2X%2C2*Y%2C2%2C2)%3Ar%2B%3Ds.charCodeAt(i-28%2Cx.fillStyle%3D'%23'%2B(r%3E%3E8%260xFFFFFF).toString(16)))r%5E%3Dr%3C%3C13%2Cr%5E%3Dr%3E%3E%3E17%2Cr%5E%3Dr%3C%3C5%2CX%3Di%263%2CY%3Di%3E%3E2%7D)()%3B
What are the alternatives? Is there something like this I can get my hands on now?
I had to be told by the Internet that it was even happening to an extent that could be noticed.
It would be interesting to have stats though.
My point is that you were entirely wrong. Web Components are not ready for primetime, they are half baked. If they were the easiest and most pragmatic way possible to build web applications people would do so.
The only thing they are the easiest and most pragmatic for is to build a simple non-form associated component that can be used across frameworks. Like a card.
> It has always been a chore in one way or another.
It's actually never been a chore to make an <input> behave properly. Something that literally every component library needs to do.
And let's be honest, making a server rendered site with some traditional Python framework is in many ways just as easy or easier than making a SPA.
There are proposals for this and most of the other issues I have with web components. But they all feel like issues that could have been covered from the beginning.
Also if you go all Lit on an app with many nested shadow doms it becomes fairly painful to test with tools like cypress.
Just look here at how much overall code is needed to do it right: https://github.com/ing-bank/lion/blob/master/packages/input/...
After you get through all the inheritance and mixins it's thousands of lines
Sure we could write the tests in python or whatever, but everyone is already using and likes Postman for the most part. And replacing the postman collections that people use for reference with a folder of scripts I don't see going over well.
I'd personally prefer something like https://hurl.dev where you have a readable file in source control, but that's not a battle I'd win at this point.
I haven't had it running in about a year though, couldn't be bothered after a move.
Jellyfin looks nice. I'll have to give it a go. I am dreading having to set everything up again if I move off of plex, rather than just grab my docker-compose file and get going.
Of course I expect a different opinion from the top 3% income tech bro libertarian bent of the HN user base. But I haven’t seen a compelling reason here to think life for the average American is better than it is for someone in the EU.
> I randomly happen upon them
It answers the question but likely not the answer they were looking for.
Personally I find that YouTube recommends decent content to me based on what I like to watch.
But it’ll recommend garbage to my kids. The problem is that the kids like the garbage.
Beyond that often YouTubers in a certain niche will mention / promote others doing similar stuff.
I do subscribe to premium just to avoid the Prager U and other ads that have no business being targeted at kids in the first place.
That it exists, it's general purpose, and given it's semantic version that it's pre-release software. That's all I know about it. I know a little more about Flutter since it has a marketing budget.
It probably wouldn't be wise to rely on either of them outside of hobby projects. Unless of course you are Facebook/Twitter/Google, aka have effectively unlimited budget and employ the people who wrote the stuff to begin with.
I've seen this but never heard of anyone using it. Do you have any notable examples of serious production apps shipped with this?
In that case explaining why you like anything is a way to shut people up who don't
I’ve always liked the rally racing driver/navigator analogy for explaining pair programming. It tends to go better if you generally follow those roles when doing it too.