Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
clktmr
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
12 ms
·
91.
▲
by
clktmr
6y ago
Go was the first language that put a real effort in building a community, best practices and a healthy, sustainable ecosystem. This starts to pay off as there are more and more actively maintained, high quality libraries available.
92.
▲
by
clktmr
6y ago
You will find exponentially less vulnerabilities the more money you spend. How much you should spend depends on how big the damage could be in case of a breach.
93.
▲
by
clktmr
6y ago
> Really, "lock free" programming is just locking critical sections with lower level hardware primitives Can fence instructions really be seen as locking mechanism? While a lock generally is bound to some data, memory fences a
94.
▲
The Arm64 memory tagging extension in Linux
(lwn.net)
85 points
by
clktmr
6y ago
|
66 comments
95.
▲
by
clktmr
6y ago
Another example is Go's runtime.LockOSThread(), which will run a single goroutine exclusively on that thread.
96.
▲
by
clktmr
6y ago
I hesitated long to make qutebrowser my main browser because of lacking password management and device synchronization. Eventually I switched and started using dedicated applications for these tasks. Qutebrowser is especially great for bro
97.
▲
by
clktmr
6y ago
Glad the author mentioned taxes, which are definitely my 'ugh field'. However I already pay a professional to do most of the work, but it doesn't help.
98.
▲
by
clktmr
6y ago
Not a Magit user, but vim-fugitive. The main reason I prefer it over the CLI is for (un)staging hunks or lines. But I still use the CLI a lot for other stuff.
99.
▲
by
clktmr
6y ago
Not true if the value refers to something like RGB color components.
100.
▲
by
clktmr
6y ago
John Carmack wrote in 2010: > There is some decent code in Doom Classic, but it is all C, and I would prefer to do new game development in (restrained) C++. > I had been harboring some suspicions that our big codebases might benefit f
101.
▲
by
clktmr
6y ago
Ok. But this doesn't justify blocking the app by the government, or does it?
102.
▲
by
clktmr
6y ago
I bet not! 1 > {} // false 1 < {} // false So the result of sorting will be random. People are fast to complain..
103.
▲
by
clktmr
6y ago
Well, what would be the expected behavior of sorting an untyped array?
104.
▲
by
clktmr
6y ago
> Futures provide pretty much everything that Context does, but without having to thread a magical value correctly through everything. It has downsides though: * Instead you have to use async/await throughout your code and suddenly
105.
▲
by
clktmr
6y ago
I am using C and Go and I don't remember ever having to deal with some kind of change in the language. Sure there were changes but with very little impact on the ecosystem. Languages evolve okay, but Rust felt more like it was just ri
106.
▲
by
clktmr
6y ago
> one year is a very long time in rust land That's the problem and stabilization doesn't solve it. Only rejecting language changes will.
107.
▲
by
clktmr
6y ago
I think the concerns are more towards the ecosystem and community, which are very curiosity-driven. I tried Rust about one year ago and nothing would compile without the nightly toolchain. After reading the Rust book there was this real
108.
▲
by
clktmr
6y ago
The first half of the article basically complains about the write()'s syscall possibility to fail. Errors can occur and you need to handle them, there is no way around it. Given that "Everything is a File", the OS shouldn&#
109.
▲
by
clktmr
6y ago
As far as I understand, it's only about including more information in the compilers json output. But that information was already available in non-json output in previos Go versions. To get explanations on the optimization decisions b
110.
▲
by
clktmr
6y ago
Disabling automatic repository housekeeping might help. It can use lots of RAM for large repositories like the Linux kernel.
111.
▲
by
clktmr
6y ago
> The solution to the fragile base class problem and other inheritance hangovers is surprisingly simple — don’t use it If OOP provides the footgun to shoot yourself, OOP is at fault. Overall the article reads as "OOP has no problem
112.
▲
by
clktmr
6y ago
This is exactly my experience. On top of that snap creates visible directories in $HOME, f-up my loop devices and snap applications can't even access /tmp. Never had any problems with flatpak and appimage. I will however use it so
113.
▲
by
clktmr
6y ago
Here I used "UUT" and "component" synonymously, which is simply all the code that should be tested. With behaviour I was referring to expected output for a given input. There is definitely a lot of cross-talk. Can you
114.
▲
by
clktmr
6y ago
I have seen too many badly written tests, so I tend to agree. Most tests will just fail on any change in the UUT, giving you lots of false positives. This ultimately results in fixing the tests instead of the UUT and blurring the initial
115.
▲
by
clktmr
6y ago
Personally as a developer I switched jobs multiple times. Most importantly because: 1. I expect to be trusted. If there is no possibility to work from a remote location and excessive time tracking (e.g. punch cards) because of a lack of t
116.
▲
by
clktmr
6y ago
You know that 'git blame' exists?
117.
▲
by
clktmr
6y ago
AFAIK you can do this with the official offline version too. What's the point of embedding it in vscode especially?
118.
▲
by
clktmr
6y ago
Isn't this just opening the drawio editor in vscode? What's the point? (genuine question)
119.
▲
by
clktmr
6y ago
Not OP, but the benefit of the filesystem implementation is probably to only fetch the data on read.
120.
▲
by
clktmr
6y ago
I can see why this is interesting from a project manager's perspective. But why would I as a developer want this, let alone pay for it? Isn't this the "developing in a browser" nightmare everybody was joking about a fe
More ›