Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
dullgiulio
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
dullgiulio
5y ago
> But it's not going to be Unix as we know it. Right, that's Plan9.
2.
▲
by
dullgiulio
5y ago
No shortcuts. Errors reach end users, and they cannot read stack traces. Every shortcut makes for bad errors, bad troubleshooting and unhappy users. Errors document code (you literally write, in English, what you were trying to do but faile
3.
▲
by
dullgiulio
5y ago
Please no. I am still fighting the battle of adding contextual information to the error using fmt.Errorf. I am tired of seeing SocketException: hostname.com as full error message.
4.
▲
by
dullgiulio
5y ago
Readable but not comprehensible. CSV is hard to beat in that sense, being somewhat "natural" like a table written on paper.
5.
▲
by
dullgiulio
5y ago
No, a normal light switch on the wall is all you need.
6.
▲
by
dullgiulio
6y ago
No, it failed because it acts on the wrong side. If you don't want to be tracked you shouldn't send cookies in your request.
7.
▲
by
dullgiulio
6y ago
This comment makes little sense. AWS is even less uniform when it comes to tools, exactly because of its organic growth. This clearly has no impact on its success nor its features. Google does have a problem with management and the org-char
8.
▲
by
dullgiulio
6y ago
Most probably all these names just indicate market day...
9.
▲
by
dullgiulio
6y ago
That's the Go runtime.
10.
▲
by
dullgiulio
6y ago
You have to implement UnmarshalJSON. Between each attempt to deserialize into a possible struct, be careful to return on errors that are not JSON serialisation errors (for example caused by reading from the underlying Reader, etc.) It'
11.
▲
by
dullgiulio
6y ago
No, that SIMD is good for string matching and Rust regex crate (written by burntsushi for 'ripgrep') makes very good use of it and is thus a nice library for implementing quick matchers.
12.
▲
by
dullgiulio
6y ago
And is Go so hard to upgrade for your application? Go the language is really best in class when it comes to keeping backwards compatibility.
13.
▲
by
dullgiulio
6y ago
Redirection is not a parameter, meaning that would still not work with this Q tool.
14.
▲
by
dullgiulio
6y ago
Another reason for people trying too look overly confident is when they are overly exposed over a certain topic. For example, if you have very narrow job titles and roles in a team ("he is our DevOps, she is our architect"...) eve
15.
▲
by
dullgiulio
6y ago
Tangentially, the adage "strong opinions, weakly held" is nonsense. If you have a strong opinion, you look like a fool if you change your mind when evidence is shown to you. It is much better to just stay humble. Show your insecur
16.
▲
by
dullgiulio
6y ago
I really cannot agree with the "just use GET" suggestion. GET must not be used for actions that modify the data server-side. Also, POST and PUT means some action is or is not idempotent. Using different methods than GET is easy in
17.
▲
by
dullgiulio
6y ago
Correct, "per difetto" means flooring a number.
18.
▲
by
dullgiulio
6y ago
I have been using double tap to select (and simply drag) on Linux for years, never had to click. And my touchpad is far from magic...
19.
▲
by
dullgiulio
6y ago
Again, disabling features is a feature given to the site developer, not to the visitor, who's actually running the code. It would be so much better if browsers were User Agents and respected user settings before the will of the site cr
20.
▲
by
dullgiulio
6y ago
Languages that to green threads don't do them for memory savings, but to save on context switches when a thread is blocked and cannot run. System threads are scheduled by the OS, green threads my the language runtime, which saves a con
21.
▲
by
dullgiulio
6y ago
That sentence is very misleading. Nobody checks the Close() error because the right thing to do is to call Err() like with the text.Scanner. I suspect the right github code search would reveal way less buggy code. https://golang.
22.
▲
by
dullgiulio
6y ago
salsa20 was added in 2012, the warning file was added into the repository in 2016 the earliest (it is not clear when--which is vary bad for security and also shows the move was not advertised.) Incompetence is a strong word on the wrong tar
23.
▲
by
dullgiulio
6y ago
Of course it is up to the application to decide case-by-case. Just keep in mind that if your query is started by a user request, but does not need to terminate in the context of the user request that triggered it, you can move the query to
24.
▲
by
dullgiulio
6y ago
Perl# basically.
25.
▲
by
dullgiulio
6y ago
Nope, this is a strawman argument you're making. Parent is asking for granular access control over these very advanced and double-edged features, which is a perfectly valid request. Having permissions is the norm for native apps on mob
26.
▲
by
dullgiulio
6y ago
It's not "they", it's Daniel J. Bernstein. That's the reason :) (If you don't know: he is a top cryptographer that can amazingly correct code. However, he also has a very big ego...)
27.
▲
by
dullgiulio
6y ago
Go follows the Plan9 system call name instead of the UNIX one. Dial is much more powerful than the UNIX dance of "getaddrinfo"+struct sockaddr init+connect(2). It might not seem much (and higher level languages usually abstract aw
28.
▲
by
dullgiulio
6y ago
Go does not have exception (exactly because of this problem.) For passing information, you use channels, which can pass more than one value back to the caller. The big thing is not running tasks in the background but the tight integration o
29.
▲
by
dullgiulio
6y ago
I don't think this is a matter of hype cycle at all. There are two things that changed: 1. Threading got much faster and lightweight. This is what Java was initially trying to work around, until it didn't have to any more. 2. The
30.
▲
by
dullgiulio
6y ago
As the article explains (I know it's hard to comment after actually reading), Java moved away from using several green threads on top of a single system thread. What Loom and Go do is to schedule green threads on a bunch of system thre
More ›