Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jjnoakes
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
93 ms
·
961.
▲
by
jjnoakes
10y ago
You seem to be arguing install scripts vs package managers, and we are all discussing something else.
962.
▲
by
jjnoakes
10y ago
None of this is an inherent problem with curl and piping however; any installer you could download and run has the same list of issues, and many of those aren't even auditable. You should redirect your anger away from curl and pipe and
963.
▲
by
jjnoakes
10y ago
Not sure why you are being downvoted, you are completely correct.
964.
▲
by
jjnoakes
10y ago
Do you have evidence that jQuery is shamed because it is mature? I've always seen jQuery not chosen (shamed doesn't seem like the right word) because it doesn't provide the level of abstraction that folks are looking for, and
965.
▲
by
jjnoakes
10y ago
I'm not taking a side here, but I would like to advocate for a fair comparison, since you have skipped all of the trade-offs in the other direction. For example, web apps are often easier to discover, easier to update, easier to manage
966.
▲
by
jjnoakes
10y ago
I don't think stats will be enough to overcome the human perception factor. Self driving cars have what I consider to be an insurmountable pr problem.
967.
▲
by
jjnoakes
10y ago
And no git command lets you change what public history looks like unless you --force the push. So the check is in a different place. That doesn't seem to me to imply that Mercurial's history is "immutable" and git's
968.
▲
by
jjnoakes
10y ago
Ok so it has nothing to do with immutability, it's just one warns earlier than the other. Thanks for clarifying.
969.
▲
by
jjnoakes
10y ago
If you "git push" after rebasing published commits, you get an error, unless you use "--force" or you pull and merge manually before hand. So I'm still not sure the distinction you are making between which one is &q
970.
▲
by
jjnoakes
10y ago
Just because the user interface or functionality didn't change doesn't imply the internals didn't change to keep it maintained and running though, right?
971.
▲
by
jjnoakes
10y ago
How do you know they didn't touch it for a decade?
972.
▲
by
jjnoakes
10y ago
> SQLite is not a good project to mention rewriting Which, as I said, is not what I'm doing. I'm only disagreeing with the premise that 100% test coverage means 0% chance of an unsafe bug existing in the code base (for any code
973.
▲
by
jjnoakes
10y ago
16 years is impressive? What would you call a 33 year old multi million line codebase still being babysat in production today?
974.
▲
by
jjnoakes
10y ago
I'm sorry, I still don't see the distinction. It sounds like in both systems the default is immutability, with commands to override that if necessary. And by the way, doesn't git rebase not mutate history? I believe it create
975.
▲
by
jjnoakes
10y ago
Can you elaborate on what you mean by immutable history, and how git lacks it?
976.
▲
by
jjnoakes
10y ago
I'm not advocating one way or the other, but I will say that I don't believe 100% code coverage guarantees that you have no issues lurking that a safer language would prevent. Now it probably isn't worth the effort for a very
977.
▲
by
jjnoakes
10y ago
I'm not disputing any of this. But it really has nothing to do with the context of this thread...
978.
▲
by
jjnoakes
10y ago
Which Linux distributions do this? I'd like to read how "most" instances of fork and exec end up with unique networks and file system namespaces.
979.
▲
by
jjnoakes
10y ago
The context of this discussion would like to have a word too...
980.
▲
by
jjnoakes
10y ago
Dynamic libraries (in the C/C++ sense) only scratch the surface. Containers give you your own file system namespace (among other namespaces), which means all of the files that make up your complicated application unit can be put togeth
981.
▲
by
jjnoakes
10y ago
How is "your own network, your own view of the file system, your own view of the process table, your own view of the user IDs, ..." the same as "processes"?
982.
▲
by
jjnoakes
10y ago
Opting for or favoring self hosting for manageable installations may not simply be a cost optimization strategy at the expense of time. For example, I personally opt for self hosting in many cases where I need more control over what runs on
983.
▲
by
jjnoakes
10y ago
IPFS?
984.
▲
by
jjnoakes
10y ago
You aren't liable for credit card fraud, but that money comes from somewhere. Today it is a small percentage charged to the vendor; do they pass it on? And tomorrow, when the problem gets worse and the fees start to climb, will you sti
985.
▲
by
jjnoakes
10y ago
> Usually that manual control comes at the cost of literally violating the language semantics and wandering into the territory of undefined behavior. What makes you say this?
986.
▲
by
jjnoakes
10y ago
> Of course type checking can catch some problems. Keep in mind, static types can also help performance, tooling (refactoring, cross-referencing, etc) and human understanding. This is not an argument for or against static types; it is si
987.
▲
by
jjnoakes
10y ago
Where in the article is that quote? The one I see is slightly different (in important ways), and in addition to that ,the 37% unaccounted for in that statistic may be "no response" or something other than "I was forced into i
988.
▲
by
jjnoakes
10y ago
Is it? Mine was worded as a polite request and his was worded as a command.
989.
▲
by
jjnoakes
10y ago
Who needs more than one dialect of C or C++? I don't. Any systems I'm interested in may not support clang, but they have C11 compilers and C++14 compilers. Rust is not interoperable with C++ as far as I know, and even if it was, I
990.
▲
by
jjnoakes
10y ago
Yes, that's exactly what I proposed.
More ›