I've fiddled with Open Props [0] a bit lately, seems like a nice middle ground! Colours/fonts/spacing/etc that look nice together are there, but it's still up to you to use them. (And you're still writing CSS, so might be a deal breaker if that's the part of tailwind you like... but CSS is rather nice nowadays.)
I might be missing something, but was this project started in 2016? I'm not sure what line in the sand you're drawing. That was some minima for developers "knowing UI actually matters" I presume?
Honestly, as someone that's been picking up OSRS again (and is actually now thinking about RS3 given all of the recent progress jagex is making on removing MTX in it!), I'd be good with that. I still like to play it myself without botting, so anything to move the bots somewhere else I think would be neat. PvP folk lose some easy kills but that's about it for impact on regular players honestly.
The problem is, the reason the bots exist now is to sell the account or farm gp. The only way this would work would be if that bot only world was gated off from the rest of the economy like special gamemode/league worlds, naturally destroying any reason most bot makers make bots. Your love of automating for sport puts you in the minority of botters sadly haha
Officially blessed OSRS private servers are on the roadmap IIRC... maybe there's a future for a bot-olympics in one of those?
I might toss it out there that upcoming changes to attr() [0] as well as typed properties [1] will add some interesting features. Being able to provide a value that's subbed into a stylesheet from the HTML itself is neat.
You can try to get by with auto-generated selectors for every possible value today, ([background="#FFFFFF"]{background: #FFFFFF}[background="#FFFFFE"]{background: #FFFFFE}...) but just mapping attributes to styles 1:1 does begin to feel like a very lightweight component.
(Note... I'm not convinced this is a great idea... but it could be interesting to mess around with.)
It has been funny seeing the tide come in and out now a few times. Though I will admit that each time, the ergonomics get better. AJAX as a pattern was pretty gnarly if you wanted to do a bit more than update a notification badge or comment box.
There's a really nice pattern of using Custom Elements [0] for that sort of JS interactivity sprinkling. You can make your web application however you want, and when you want the client to run some JS, you just drop in `<my-component x="..." y="...">...</my-component>` with whatever flavour of HTML templating you have available to you. (also possibly with the is= attribute in the future [1], which will let you keep more of the HTML template out of JS)
It saves you the hassle of element targeting and lets you structure that part of your app a bit more without going overboard on "everything is a react component, even the server bits".
Want something "server side generated" in that JS? Just render it in attributes/body/a slot element/a template element, and expect to pick it up in the JS side of things. Feels like how it's supposed to be... and there's no framework required!
Custom Elements do start to feel like the dream of the Knockout-era web of "Progressive Enhancement" is finally almost entirely out of the box in the browser. Especially ignoring the Shadow DOM and using Light DOM to style your unpopulated or static rendered fallback states as close to your "live" JS-driven state can lead to some very good experiences, including and especially when JS is disabled (or erroring).
I think it's just a bit of an obscure way of saying total subscribers. "${verb}ership" like "readership" meaning the number of subscribers + casual readers of a magazine [0], or "viewership" meaning a TV show's total viewers/ratings [1]
I don't think I've ever heard listenership in that same context though, so they might have just made that up. haha
I’ve been more and more confused by Apple’s product positioning for MacOS. They still have a sizeable “pro” (emphasis not sarcasm) market that spans across a very aspirational set of careers: Film, YouTubers, developers, photographers, artists, musicians, etc.
Considering how many people only buy a MacBook PRO no matter what they plan on doing with it, they really need to keep the actual salary-earning pros happy with it or else it’ll lose all credibility. A Mac in a recording booth has a look to it that sells well, but that aesthetic won’t last if you stop seeing them. Being an effective tool for the pro minority should honestly be the priority for MacOS, even at the cost of making it incongruous from iPadOS/iOS. *
* disclaimer: what do I know honestly haha, I’m sure they’ll print money anyway.
I mean, if there was only 1 engineering firm that made the iBridge, which represented nearly a quarter of all bridges out there, they might last a bit longer. They really made the bridge experience truly inspiring with the all-new glass I-beams!
It would be interesting to see you compare notes with https://news.ycombinator.com/item?id=46446021. You both seem to have similar uses for windows, but totally opposite experiences.
[0] https://open-props.style/
reply