Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
motorest
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
10 ms
·
151.
▲
by
motorest
1y ago
> So basically react class components? It definitely was not easier in those days. Yes, class components. Function components help in reducing boilerplate code when all you want to do is put together a component that is a thin wrapper ov
152.
▲
by
motorest
1y ago
> If it's not feasible to audit every single dependency, it's probably even less feasible to rewrite every single dependency from scratch. There is no need to rewrite dependencies. Sometimes it just so happens that a project ca
153.
▲
by
motorest
1y ago
> I think this is a good argument for reducing your dependency count as much as possible, and keeping them to well-known and trustworthy (security-wise) creators. I wonder to which extent is the extreme dependency count a symptom of a st
154.
▲
by
motorest
1y ago
> This just reeks of bigotry or at they least of disingenuousness ...and yet, Russia today is overtly and unapologetically engaged in genocide and ethnic cleansing in it's invasion of Ukraine, not to mention what the regime has been
155.
▲
by
motorest
1y ago
> The problem that React originally aimed to solve was creating reactive user interfaces in facebook's monorepo monolith where 1,000+ software engineers are constantly churning code. Nonsense. React's selling points have nothin
156.
▲
by
motorest
1y ago
> 1. It's a solution meant for highly interactive app-like websites, not static-content driven websites like ecommerces. React in this context is just the wrong tool for the problem that will give you a huge array of performance, bu
157.
▲
by
motorest
1y ago
> So rather than focusing on how Microsoft/npm et al can prevent similar situations in the future, (...) There's some ignorance in your comment. If you read up on debug & chalk supply chain attack, you'll end up discov
158.
▲
by
motorest
1y ago
> Why are people using React to write simple ecommerces? What leads you to believe React is not well suited to simple ecommerce sites?
159.
▲
by
motorest
1y ago
> React isn’t just "winning by default" It's winning because at the core it's just JavaScript function composition. A component is a function, conditionals are `if (...) { ... } else { ... }`, loops are `map()`. JSX i
160.
▲
by
motorest
1y ago
> New day, new npm malware. Sigh.. This. But the problem seems to go way deeper than npm or whatever package manager is used. I mean, why is anyone consuming a package like colors or tinycolors? Do projects really need to drag in a rando
161.
▲
by
motorest
1y ago
> Paradoxically in SW development complex things often appear because it's easier (simpler) to 'just add this check here' instead of rethinking (and remaking) previous solution with updated understanding. I think the issue
162.
▲
by
motorest
1y ago
> You gave an example where the use of react would be justified to prove your point. You could have also given one where it isn't. The article is about the latter. Not really, the article is about a belief some other approach would
163.
▲
by
motorest
1y ago
> Yeah, except that a sprinkle becomes a dusting, and then a dusting becomes a coating, and then a coating becomes a clog of dust bunnies, and it's often hard to tell when you need to stop and do it a better way when the business si
164.
▲
by
motorest
1y ago
> The argument is valid and doesn't need over analyzing. No, it isn't. A big part in your failure to understand the problem is your refusal to look at what you're doing, which you try to dismiss as "over analyzing&quo
165.
▲
by
motorest
1y ago
> Sure. The point is, people use React for everything, even static web sites, not only for creating reactive user interfaces. They do it because someone else told them so. No, not really. There is more to picking up a tool than some rand
166.
▲
by
motorest
1y ago
> The article argues that while React solves a problem, not everyone actually has a problem that requires the complexity of React (i.e. "Build pyramids if you must"). I think this argument isn't valid. The problem that Rea
167.
▲
by
motorest
1y ago
There's a silver lining in raspberry pi and it's clones being so relatively expensive: they create a market and demand for hackable devices. In an age with so much pressure to plug every single digital hole, these devices bring so
168.
▲
by
motorest
1y ago
> Because most "woke" stuff is made up or blown out of proportion by people on the internet. I think you are misinterpreting the issue. I'll explain why. There are attention-seekers which were given access to platforms wit
169.
▲
by
motorest
1y ago
What an interesting gadget! It looks like it has most of the features of an Orange Pi Zero, but at around 1/5th of the price.
170.
▲
by
motorest
1y ago
> Since vectors are usually normalized to the surface of an n-sphere (...) In classification tasks, each feature is normalized independently. Otherwise you would have an entry with feature Foo and Bar which depending on the value of Bar
171.
▲
by
motorest
1y ago
> C++ has a lot of features which are not best practices. For example, you're not supposed to use the builtin arrays anymore, in favor of vector<>. Again, you know better than this. I don't know why you are making these c
172.
▲
by
motorest
1y ago
> What do you think of C and C++ coming with extensive guides for best practices and what features to not use? I feel that this is a disingenuous point and that you know better than this. For example, the poster child of C++'s "
173.
▲
by
motorest
1y ago
> I think D failed to gain widespread traction for other reasons though: D's selling only proposition was providing C++11 features in a point in time between C++98 and C++11 when the C++ committee struggled to get a new standard out
174.
▲
by
motorest
1y ago
> Love this quote. An love the intent. What intent do you think it has? That proposals are still being worked on and haven't been published in a specification yet?
175.
▲
by
motorest
1y ago
> Like the google people who can't convince them and went on to create carbon? Lots of people in mega-companies set forth to reinvent the wheel. I think we have enough track record to understand that the likes of Google don't w
176.
▲
by
motorest
1y ago
> (...) "You shouldn't be writing new code in C++ if you want guarantees". I'm afraid context is required to actually understand what was said. For example, it can mean anything including very obvious things like stat
177.
▲
by
motorest
1y ago
From the article: > Profiles seem less radical and more adoptable, a safer-by-default C++ without forcing the Rust model that aims to tackle the most common C++ pitfalls.
178.
▲
React Native – About the New Architecture
(reactnative.dev)
1 points
by
motorest
1y ago
|
0 comments
179.
▲
by
motorest
1y ago
> So, one could make a similar article saying "Myocardial infarction may be caused by sugar consumption" (... One could apply the same flawed logic to claim that propensity for myocardial infarction may cause certain bacterial
180.
▲
by
motorest
1y ago
> Isn’t it obvious that a heart attack could be caused by a myriad of issues? I think you not only missed the point but also are doubling down on your mistake by conflating correlation with causality. You don't conclude that burger
More ›