Hacker Newsnew | past | comments | ask | show | jobs | submit | snshn's commentslogin

Nice, but Mikado is faster


Here the creator of Solid compares it to Mikado: https://github.com/solidjs/solid/discussions/485



...when SolidJS isn't niche enough!


Performance is not necessarily worth maxing at all costs.

Is that project even maintained still? GitHub looks...quiet.


Could you please it put it in the store? Or add to brew?


Did you look at the readme? It’s right there at the top dude.


I use Firefox with Tree Tabs extension for that.


What's with the TST comments in this thread, this thing has more in common with PaperWM than with TST. Maybe you people should read.


Based on comments here either people don't know TST or don't actually care about this functionality beyond seeing it as interesting.


I'm on mobile right now, can't inspect how they did the web fonts. Is it JS-based, or they used something similar to this https://github.com/Y2Z/invisible-ink?


React has terrible performance


Poorly written React (which is a lot of it) has terrible performance. Properly written React (just like properly written anything) has great performance.

The reason you experience it as terrible is because it's today's visual basic: it's so easy to start with that everyone does, without needing to understand programming or specifically how React works. You can just throw shit together and it'll work. It's empowered an entire generation of web and app makers, with the cost being "and they're not good at that, through no fault of their own, but they are just good enough to be dangerous".


It isn't even that new, in terms of approach... a LOT of game and simulation would work with state driven rendering... each frame is rendered against the current state. Similar workflows to React+Redux were in pretty broad use, the tools just brought it to web development... from there, React as a model for UI abstraction became more popular for other applications outside web use. It makes a lot of sense.


If you already understand the idea behind state driven updates, you're already writing better React than the majority of folks using it. React made it easy enough to write working UIs without having a clue what's actually happening, when, and why. (which is also why there's a never-ending stream of stackoverflow questions about why obvious state mutations don't immediately kick in)


In fact, afair react was made to make the page faster. (as dom manipulation was WAY slower back then)


It has adequate performance and the ease of development is worth it not being the most performant way to do things.


Hey, at least no memory leaks this time! Ü


So true. Monolith is using libraries made by Mozilla for their Rust-driven browser engine (which I believe, never happened to be). I really would love for it to be a part of some browser one day, the demand is clearly there. Nobody likes to have a file+folder abomination on their drive, or some shady formats like .webarchive


MHTML support is planned, there's a couple of other problems that need to be resolved first, but it's a good format for archiving, been requested many times


Thanks for the reply. Very exciting. I would love to see MHTML support on this.


It's only logical. Attractive people use apps and social skills to sleep with multiple other attractive people, while unattractive people masturbate and refuse to sleep with other unattractive people.


While I agree, the dynamics here is slightly unbalanced between the genders.


Those are garbage. Stick with HILTI, Metabo, Fein, Festool. Or Japanese-made Makita, as the last resort.


Maybe explain why you need to buy very expensive tools and everything else is garbage?

Just about every contractor around here (USA based) is using Milwaukee, Dewalt or Makita. These folks make a living with their tools and don't have patience for junk. Even lower tier brands like Ryobi are more than capable for home use. I got a lot done around the house with a basic Hitachi drill and corded Skil saw before treating myself to some fancier stuff.


I've run into a few contractors who have Ryobi as well, and are fine with them. They're sufficient for a lot of tasks, and most contractors end up with multiples of any tool anyway. One actually said "I may go through two Ryobi tools while you go through one, but it's still cheaper, and I worry less about losing or wrecking it."

I've yet to meet a contractor who's brand loyal to the point of only using that brand. Most have two or three brands they tend to go to.


There is the market segmentation to be considered: Ryobi is owned by the same holding that owns Milwaukee so they make sure a Ryobi tool does not perform on par with a more expensive Milwaukee equivalent. So if you do, say, electrical work, you can use a Ryobi impact because you don't really care how fast you screw a dozen fasteners you'll need in a whole day. But if you install cabinets/decks and need to put in thousands fasteners a day then you will want the fastest impact, which won't be a Ryobi by far.

As for brand loyalty - it comes from the fact that batteries are more expensive than the tools. A handyman or a two people crew on a small job can have five different batteries with five different charges for ten different tools in the truck without much problem. A crew of ten people working on the same site for days will need multiple batteries per tool and if they try to use different systems they will end up with people waiting for a free outlet so they can charge and work for a couple more hours before they will need to wait again. It's much easier to set up one charging point and pool charged batteries for everyone to use.


I know some contractors with Harbor Freight tools that they're moderately annoyed haven't died yet. Buy it once to throw away and it just keeps working.

Lots of the super price brands like Festool are more ... showoff I almost feel.


AvE on YouTube tears these tools down and compares components: https://www.youtube.com/playlist?list=PLvgS71fU12Mbx-w18Chu_...


This channel looks awesome. I wanted upgraded tools this Christmas (and bought some) but didn't go this far down the rabbit hole.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: