Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
funcDropShadow
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
211.
▲
by
funcDropShadow
3y ago
That is OCaml. Not that I claim OCaml is extremely fast, but it has a very predictable performance. Which is imho even more important than being the fastest in certain benchmark problems.
212.
▲
by
funcDropShadow
3y ago
The Java ecosystems initially started with optimizing Java compilers. That setup could benefit from direct hardware support for Java bytecode. Later, it was discovered that it is more beneficial to remove the optimization from javac in orde
213.
▲
by
funcDropShadow
3y ago
That article also states that using a standard Git feature, shallow clones, you go from 20min to 90s. Most of the problems touched upon in the article are about state management for local environments, yes that can be tricky. And it can tak
214.
▲
by
funcDropShadow
3y ago
True, that is one those interactions between users that I mentioned. But the amount of people having the code checked out and poking around its history is only limited by capacity to clone the repository. All other operations are just local
215.
▲
by
funcDropShadow
3y ago
> The biggest drawback of Git is its limited scalability - both in repository and file sizes, and the number of concurrent users. How did you come to the conclusion Git isn't scalable in the number of users? There is no limit in the
216.
▲
by
funcDropShadow
3y ago
They used --force which is usually the flag to say: Here there be dragon. Be careful.
217.
▲
by
funcDropShadow
3y ago
So, the answer is No.
218.
▲
by
funcDropShadow
3y ago
Did you try git-annex instead of git-lfs?
219.
▲
by
funcDropShadow
3y ago
Until the day, the company is target by a ransomware group and everything is switched off in panic. Or the day the network connection of a building goes down. Requiring a REST api in the cloud for every VCS is command bytes hard then. We ha
220.
▲
by
funcDropShadow
3y ago
Even a force push doesn't destroy the reflog or runs the GC server-side. I wonder how you can accidentally loose data with Git. I've seen lot's of people not being able to find it, but really destroying it is hard.
221.
▲
by
funcDropShadow
3y ago
> The option of doing away with the hardware keyboard and going touchscreen-only was always there and always up for discussion, but for the longest time not easy due to the power and performance envelope at the price point. Not only the
222.
▲
by
funcDropShadow
3y ago
What many people ignore from Ahrens description of Luhmann's Zettelkasten, is that it isn't an indexing system to find pre-existing knowledge/texts. It is the place where he stored his own insight, his own summaries, his own
223.
▲
by
funcDropShadow
3y ago
> Those who want consistency will need to provide it themselves, in the form of tools like tree-sitter. Or in the form of radical simplicity. For the purpose of the parents discussion Lisp is the ultimate minimal language. Since, the syn
224.
▲
by
funcDropShadow
3y ago
> A lot of great software ideas died quietly because there wasn't a sanctioned route to scale the learning curve. A lot of great software is dismissed because people pretend there should be no such thing as a learning phase.
225.
▲
by
funcDropShadow
3y ago
There is no reason why a better shell couldn't show tool tips over command names or flags, assuming there is support for it in a terminal emulator. Even without support from the tooltip it would be possible to show some info about the
226.
▲
by
funcDropShadow
3y ago
> Even if the GUI is completely unfamiliar, and you have to learn it, you can still see the different buttons, menus etc. Unless the GUI uses some material style nonsense. Then you have to guess where buttons are. Menus are so uncool. Ev
227.
▲
by
funcDropShadow
3y ago
> #1 it does fine on By default, I'd say no. But with a few config settings and one or to aliases it is excellent. > #2 fails because it uses jargon that's internal Git state, staging, index, etc. Yes, it uses it's on j
228.
▲
by
funcDropShadow
3y ago
Is there some writeup how to achieve that?
229.
▲
by
funcDropShadow
3y ago
> restic on the other hard is still incredibly slow Restic's performance to scan the local disk depends on the target you are storing the backup at. I switched recently from a local NAS server to AWS. Before that change scaning 300
230.
▲
by
funcDropShadow
3y ago
Some chisels and Japanese saws. /s Honestly, what do you expect to get back from such a question? The answers are completely useless to anybody, unless they provide some context about the project. Is it a piece of software? Should it r
231.
▲
by
funcDropShadow
3y ago
But, if the subscription provider goes out of business or changes the product, I have to be prepared to spend more time to find an alternative. So, if I want to keep a project long term, I'd avoid subscriptions.
232.
▲
by
funcDropShadow
3y ago
> Considering the specific issues highlighted in the article, it's curious why there hasn't yet been the development of an accessible, user-friendly operating system featuring large buttons and straightforward menus Because no
233.
▲
by
funcDropShadow
3y ago
But, isn't the separation of the control-flow into chunks, either separated by async/await or by sepration between call and callback, a form of cooperative thread yielding on top of preemptive threads? If that isn't true for
234.
▲
by
funcDropShadow
3y ago
Async programming is not an alternative to semaphores and mutexes. It is an alternative to having more threads. The substantial drawback of async programming in most implementations is that stack traces and debuggers become almost useless;
235.
▲
by
funcDropShadow
3y ago
In the last 15 to 20 years asynchronous programming --- as a form of cooperative multi-tasking [1] --- did gain lot's of popularity. That was mainly because of non-scalable threads implementations in most language runtimes, e.g. the JV
236.
▲
by
funcDropShadow
3y ago
Independent of the origins of the 80 character line lenght rule. Some say it originated on punch cards. It is a useful rule. Classical news papers also have narrow columns. Why? Because it helps reading.
237.
▲
by
funcDropShadow
3y ago
> tries to limit my commit messages to 50 or 55 characters The tools try to limit the summary line of Git commit message to 50 characters. Not the whole message. That is a useful convention. The usual convention is described here: https
238.
▲
by
funcDropShadow
3y ago
What do you do for refactorings?
239.
▲
by
funcDropShadow
3y ago
> It's just super impractical. The work is discussed / documented in the project management systems I agree, it is super impractical to have to read the whole discussion again instead of having a comprehensive description of th
240.
▲
by
funcDropShadow
3y ago
And it allows applications to display a PDF with an A4 page at 100% to have exactly the size of an A4 paper.
More ›