Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
prepperdev
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
1.
▲
by
prepperdev
6y ago
Yes. That very example shows why itis hard to write fast program in Ruby. It's not even the interpreter (which is slow), but it's that Ruby is pure magic. I was never able to understand what happens, when I looked at a particular
2.
▲
by
prepperdev
6y ago
Craigslist approves: https://sfbay.craigslist.org/
3.
▲
by
prepperdev
6y ago
Monorepos are underappreciated. - Dealing with cross-repositories changes is unproductive. - Relying on external servers (git / npm / whatever) is risky. - Visibility of what goes to your servers is never easy without having every
4.
▲
by
prepperdev
6y ago
Essence: "A single associate assigned to a specific production line working between the production dates specified (12/14/2020 – 12/21/2020) was found to be using an improper torque wrench technique". A case fo
5.
▲
by
prepperdev
6y ago
The counterpoint is valid (rising seas don't help), but then we have Saint Petersburg ([1]) that's literally build on top of swamps and occupies multiple islands. It has a first class subway ([2]). It's a little deeper than r
6.
▲
by
prepperdev
6y ago
Amazingly, the chat example still works: $ ssh chat.shazow.net * prepperdev joined. (Connected: 35) [prepperdev] anyone here? :)
7.
▲
Why aren’t we using SSH for everything? (2015)
(medium.com)
4 points
by
prepperdev
6y ago
|
1 comments
8.
▲
by
prepperdev
6y ago
What are the limits for the number of layers? 176 seems like a large enough number to believe that a few thousands are a possibility. Is the tech any close to a bottleneck, or they will keep growing them up?
9.
▲
by
prepperdev
6y ago
That would be up to a specific OS to decide which guarantees on stack size limit would it like to provide. But I agree that it's a valid concern, and not all possible vDSO implementations are reasonable.
10.
▲
by
prepperdev
6y ago
vDSO is a good way to mitigate issues like these. It's also a better stable ABI than libc, and easier to maintain than pure kernel ABI (like Linux does), because nobody forbids the kernel to inject different vDSOs to different binaries
11.
▲
by
prepperdev
6y ago
This is covered by their FAQ: https://gemini.circumlunar.space/docs/faq.html , Section 2.5 "Why not just use a subset of HTTP and HTML?"
12.
▲
by
prepperdev
6y ago
What I meant is having markdown pieces within code regions in a text/gemini doc. Imagine a code review tool that tries to show a diff as text/gemini.
13.
▲
by
prepperdev
6y ago
Gemini is a cool piece of simple tech. I had a genuine pleasure reading the spec: https://gemini.circumlunar.space/docs/specification.html I've entertained an idea to build a set of tools for contemporary developm
14.
▲
by
prepperdev
6y ago
Yes. I definitely had the vibe of 'Get the Facts' from the Microsoft Linux-smearing campaign circa 2004 ([1]). 1. https://en.wikipedia.org/wiki/Criticism_of_Linux#Criticism_b...
15.
▲
Subversion vs. Git: Myths and Facts
(svnvsgit.com)
3 points
by
prepperdev
6y ago
|
4 comments
16.
▲
by
prepperdev
6y ago
First of all, kudos for trying to find new ways to fund open source. Those are needed. This approach might work well for issues which require a lot of thought, but produce a simple fix and can be easily merged This might go horribly wrong i
17.
▲
by
prepperdev
6y ago
Bloomberg maintains an excellent dashboard that tracks vaccination in the US and worldwide ([1]). It shows that California is one of the slowest states with only 37% of received vaccine administered. Top five states are North Dacota (77%),
18.
▲
by
prepperdev
6y ago
Excuse me? While my account is relatively young (13 days), it's not one day old. You can also look into my comments over this time. So, the accusation is clearly off.
19.
▲
by
prepperdev
6y ago
snaps are tied to the proprietary Ubuntu store and they are not available on all of the Linux flavors. For instance, I don't see snapd on Alpine Linux: $apk search snapd $ Not cool, I think.
20.
▲
by
prepperdev
6y ago
I don't believe it's a joke. It still might be a deliberate lie (a random twit is not a real source of knowledge), but so far this is consistent with what we already know. See https://news.ycombinator.com/item?id=2
21.
▲
by
prepperdev
6y ago
Copying their requirements as text (original grammar preserved, including GB and Gb confusions). It's a good glimpse of what unlimited cloud budget does to companies. I quote: """ * 40x i3.Metal instances (64 vCPU's
22.
▲
Parler Hosting Requirements
(twitter.com)
59 points
by
prepperdev
6y ago
|
29 comments
23.
▲
by
prepperdev
6y ago
Recently, I migrated my personal dev laptop from Ubuntu to Alpine Linux. It took a day, but everything works now, including hidpi stuff. No big issues so far and I am in the process of migrating my home server to Alpine.
24.
▲
by
prepperdev
6y ago
Debian policy is very sane (no network access during build), but it does seem like modern software just assumes that the Internet is always available, and all dependencies (including transitive) are out there. The assumption is a bit fragil
25.
▲
by
prepperdev
6y ago
Key quote: "We have become extremely dependent on conda and conda-forge. We must think of their sustainability." Then it talks through the steps being taken to reduce dependency on Anaconda Inc. While the company proved to have a
26.
▲
by
prepperdev
6y ago
It really depends on how small or large your organization is. If it's a single repo with a single branch, sure. No need for explicit backups. If it's tens of repos with multiple important branches in each, then it would be very da
27.
▲
by
prepperdev
6y ago
That's not necessarily true. If your organization has tens of repositories with multiple important branches in each, all odds that at least some of those branches are lost. Proper backups of all repos are an answer, of course.
28.
▲
by
prepperdev
6y ago
Yes, as answered in another branch, it's possible and reasonable to setup continuous / daily backups, if you're using a hosted Git service (Github or not). This will mitigate the risk of losing access to the code. It's n
29.
▲
by
prepperdev
6y ago
Yes, making daily on-premise backups would mitigate the risk of losing source code. That applies to everyone, not just Iranian developers: setup daily backups of all your code.
30.
▲
by
prepperdev
6y ago
That sounds great, but it's a very fragile state of things. While it certainly makes lives of Iranian developers easier, it does not make it a good idea to put their code there: laws change, and quickly sometimes.
More ›