Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
icedchai
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
34 ms
·
781.
▲
by
icedchai
1y ago
I've done modem calls over VOIP. Any connection above 2400 is incredibly unstable for the reasons you describe.
782.
▲
by
icedchai
1y ago
My first modem was 1200... In the early 90's, I got a 9600 baud modem, which is where it felt like things were really taking off. A whole page of text in less than a couple of seconds! I ran my own BBS on 9600 for years.
783.
▲
by
icedchai
1y ago
I also vaguely remember there being FCC power limitations on (some?) 56K modems, limiting them to ~53K max. Also, even with a 56K connection, upload speeds were still limited to 33.6K max. Fortunately, I got cable internet around 1997 and n
784.
▲
by
icedchai
1y ago
Yes! Also, early ISPs were often massively over subscribed. They might have fractional T1 line coming into a POP (example: 384Kbit line) with 100 modems off of it. At peak times, you not only got busy signals, but when you did get through,
785.
▲
by
icedchai
1y ago
You may have connected at 56K, but it was rare to see in practice. I worked for an ISP and we could see all the stats. We had Ascend Max equipment. To add further confusion, your modem may have been reporting the serial port rate, not the
786.
▲
by
icedchai
1y ago
Same. There are tons of people are spend more time organizing 'TODOs' than actually doing them.
787.
▲
by
icedchai
1y ago
On top of that, almost nobody actually connected at 56K. You needed a perfect phone line. Still, compression did help a bit. Dialup latency sucked though. It was 100's of milliseconds. I had a friend with a 56K ISDN line (data over v
788.
▲
by
icedchai
1y ago
The problem with Jira (and other tools) is it inevitably gets too many customizations: extra fields, plugins, mandatory workflows, etc. Instead of becoming a tool to manage work, it starts getting in the way of real work and becomes work it
789.
▲
by
icedchai
1y ago
I have at least 10 accounts myself.
790.
▲
by
icedchai
1y ago
It's definitely more of an education issue. I still run into "IT" people that instinctively disable IPv6 no matter what. How do we fix this? The sad thing is IPv6 is actually easier in many respects: subnetting is simpler, no
791.
▲
by
icedchai
1y ago
It definitely seems worth checking out. I've been using FastAPI for a few years now.
792.
▲
by
icedchai
1y ago
Bring back the 90's. ;) The memories of spacer gifs...
793.
▲
by
icedchai
1y ago
Possibly. For comparison, how long did the dot-com bubble last? From roughly 1995 to early 2000.
794.
▲
by
icedchai
1y ago
Same. Then someone edits the form and changes the names of several inputs, obsoleting much of the previous work, some of which still needs to be maintained because multiple versions are floating around.
795.
▲
by
icedchai
1y ago
Yes. You stepped over the line trying to do the manager's job. ;) One manager told me he didn't believe person X's performance was a problem because the work was getting done. The work was getting done by other people. I o
796.
▲
by
icedchai
1y ago
It depends. I worked at a company with tons of title inflation. The first layer of management was referred to as "director." One of the "directors" literally had one report. The organizational hierarchy was bizarre.
797.
▲
by
icedchai
1y ago
Firing someone "for cause" is an incredibly long and difficult process at many organizations. They eventually get put on a PIP for 3 to 6 months, meanwhile they are looking for another job and continuing to drag down performance o
798.
▲
by
icedchai
1y ago
Performance management is challenging and has been a problem with my previous managers. I point out that person X is not doing their job well, not reviewing PRs (stamping LGTM on everything after about 30 seconds), writing buggy code, writi
799.
▲
by
icedchai
1y ago
This sort of corporate rot even infected smaller companies. Teams where we have a 1:1 PM to Engineer ratio, 3 person dev teams with a dedicated "engineering manager" that invents useless meetings to justify their position, individ
800.
▲
by
icedchai
1y ago
It's been well over 10 years since I worked with, almost 15. I remember issues with keeping multiple devices in sync, syncing them back up when a user comes back online, especially with multiuser chats. I understand that is probably be
801.
▲
by
icedchai
1y ago
I wasn't trying to be specific, just an opinion on what I experienced 10+ years ago. Others are welcome to work with the protocol and develop their own opinions.
802.
▲
by
icedchai
1y ago
I briefly worked on an XMPP client around that time. It cemented my opinion that the protocol was an absolute abomination.
803.
▲
by
icedchai
1y ago
Wireguard is so much simpler than those other options. IPSec is a mess.
804.
▲
by
icedchai
1y ago
I worked quite a bit with gevent'd code about 10+ years ago and also agree. Dealing with function coloring is incredibly non productive. This is one of the things "go" got right.
805.
▲
by
icedchai
1y ago
When I went to university in the 90's, Scheme was used in a couple of early courses. I had already learned C and Java on my own, but greatly enjoyed how Scheme made me think about problems differently. (I didn't learn Python until
806.
▲
by
icedchai
1y ago
DEC equipment had something similar. A 6 pin "MMJ" connector. It almost looks like RJ45 except the clip was off center. I also remember some 90's terminal servers that had enormous "octopus" cables. There was a sing
807.
▲
by
icedchai
1y ago
Now, yes. But eventually, we'll reach a tipping point where that isn't necessary. When? Your guess is as good as mine.
808.
▲
by
icedchai
1y ago
I’m hoping IPv4 is obsolete by that time. That’s a good idea though.
809.
▲
by
icedchai
1y ago
I was an early Internet user (early 90's.) They gave them out to anyone who asked back then.
810.
▲
by
icedchai
1y ago
A ton of old equipment would need to be upgraded to use 240/4 for IPv4 unicast. We'd run into weird issues where it works for some people and not others. I'm not convinced. If this was done 25 years ago, maybe.
More ›