Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
Sankozi
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
61.
▲
by
Sankozi
10mo ago
People using it wrong. It definitely should not be that popular. 95% of times when I see it I consider it a tech debt. You should be using it in rare cases when you want to verify very complex code that needs to be working with strict requi
62.
▲
by
Sankozi
11mo ago
In the same post you are arguing for and against "slippery slope". Either it is possible to easy change law to make it worse ("slippery slope" is valid objection) or changing law is "much harder than doing nothing&q
63.
▲
by
Sankozi
1y ago
The thing is you don't need to do this in "normal" system where dependencies are stored in local cache and build tool is using them during the tasks. If JS had a proper build tool then creating such directory inside project w
64.
▲
by
Sankozi
1y ago
You still need to have those symlinks checked. For example you switch branch to one with updated package.json, now you need either to check symlinks or you risk to have incorrect build. Introducing a directory that needs to stay in sync wit
65.
▲
by
Sankozi
1y ago
This is literally not possible. If you have local dependency repo and dependency manifest, during the build, you can either: 1. Check if local repo is in sync - correct build, takes more time 2. Skip the check - risky build, but fast If the
66.
▲
by
Sankozi
1y ago
It is possible to set version ranges but it is hard to see this in real world. Everyone is using pinned dependencies. Version ranges are really bad idea which we can see in NPM.
67.
▲
by
Sankozi
1y ago
This is not a good idea: this leads to longer build times and/or invalid builds (you build against different dependencies than declared in config). Having dependency cache and build tool that knows where to look for it is much superior
68.
▲
by
Sankozi
1y ago
Flash performance is still better than current web stack's. Probably will always be - you could write non trivial games that would work on 128MB memory machine. Currently single browser tab with simple page can take more than that.
69.
▲
by
Sankozi
1y ago
You don't have to buy a new car. Used ones are dirt cheap (soon this will include EV too).
70.
▲
by
Sankozi
1y ago
Nobody is planning for this magical instant 1 to 1 switch to EV. It will happen gradually. Most of the world is playing catch up with Norway (97% EV market share) - if their grid will handle the transition then it is possible. If it will no
71.
▲
by
Sankozi
1y ago
Where is it happening? Where buying a car is really expensive? The only places that come in mind are those packed cities that require a parking place for a car. Nothing to do with EV.
72.
▲
by
Sankozi
1y ago
It is not package managers. It is due to the poor NPM ecosystem: lots of crappy packages (like left-pad), auto updates, lots of dependencies, post install scripts, insecure language. These security problems happen much less often in other e
73.
▲
by
Sankozi
1y ago
No they are not as susceptible - auto updating dependencies, post install scripts and culture of thousands of crappy micro packages (like left-pad) is mainly a NPM issue.
74.
▲
by
Sankozi
1y ago
You are commenting under blog post that tried to explain it and got it wrong. It is not simple. Examples: - algorithm with O(2^n) complexity might be faster for your problem than O(1) algorithm - the same algorithm may be O(2^n) or O(n³) de
75.
▲
by
Sankozi
1y ago
More intelligent specie (AI) designed by specie (humans) that has history of eradicating less intelligent species (neanderthals). I don't see how anyone can't see the problem.
76.
▲
by
Sankozi
1y ago
You are forgetting that we are talking about AI. That AI will be used to speed up progress on making next, better AI that will be used to speed up progress on making next, better AI that ...
77.
▲
by
Sankozi
1y ago
Unless the documentation says that Math.Pow just returns the result of calling some other code (it doesn't do that), the bug is both in the Math.Pow and underlying library. It should be reported and tracked in both.
78.
▲
by
Sankozi
1y ago
Unix philosophy is "do one thing, do it well". Left-Pad forgot about the second part. For me it was surprising that so many projects used this naive implementation. Nonnaive implementation is faster and much smaller.
79.
▲
by
Sankozi
2y ago
Better - estimate complexity so things like "this algorithm will take 1234 + 2 n + 500 m operations " for our use case Much better - research (not always possible) Best - benchmark it using realistic data from your use case
80.
▲
by
Sankozi
2y ago
Let's say you have 2 algorithms. Constant time O(1) and exp time 2^n. It seems constant time is better. But in fact it runs always 42 years. While exp one starts to run longer than millisecond for sizes bigger than number of particles
81.
▲
by
Sankozi
2y ago
Yes bubble sort usually will take more time, but big O notation does not say that quick sort will be better for your real world problem. Complexity estimations or just benchmarks are much better at that. You should never limit yourself to b
82.
▲
by
Sankozi
2y ago
Yes, lots of these problems assume fantasy infinite world. Big O notation also suffers from this - it's almost useless for real world problems.
83.
▲
by
Sankozi
2y ago
If it was really designed for representing JS objects then it was really bad job. Neither JSON supports JS objects (lack of NaN) nor JS supports JSON (lack of arbitrary precision decimals).
84.
▲
by
Sankozi
2y ago
How do you define a framework if React is not one? It is one of more clear examples of a framework: - calls your code - heavily affects how the code is written - requires significant build configuration (could even be argued it is something
85.
▲
by
Sankozi
2y ago
If closed source solution of bankrupt company used closed source solution of a non-bankrupt company then you just need a new licence. If non-bankrupt company is not issuing new licences then it is not supporting its software -> it needs
86.
▲
by
Sankozi
2y ago
But it has been explained many times from many angles. * SELECT first makes autocomplete hard * SELECT first is the only out of order clause in the SQL statement when you look at it from execution perspective * you cannot use aliases define
87.
▲
by
Sankozi
2y ago
Lobbying covers most of the corruption in the 1st world. Accepting gifts is risky, they are often forbidden or at least need to be reported. It is much easier to accept legal bribes - donations, speaker invitations, PAC support. Professiona
88.
▲
by
Sankozi
2y ago
C++ is weakly typed language with undefined behaviours baked in. It definitely did not get "things" right. And also - you can get nullable references. The following compiles (and often runs) without a problem: int functionWi
89.
▲
by
Sankozi
2y ago
"It is not a goal to require programs to explicitly account for all null values that might occur; unaccounted-for null values may cause compile-time warnings, but not compile-time errors" Unfortunately this will only be checked at
90.
▲
by
Sankozi
2y ago
There are very few languages that got "things" better than Java (if I understand kstenerud correctly): * Haskell * Rust * C# (barely) with other .NET languages Any others? If "Java is like a third world village learning about
More ›