planteen
planteen on Hacker News
30 year mortgage rates are around 3.65% this week. So if a buyer puts down 20%, that will be around $259k in interest over the life of the $400k loan, putting the total interest at half of what you said (~$760k total the life of the loan versus $1 million).
While certainly the US population is aging and slowing in growth rate, I have not seen any predictions for a population decline by 2050 or even 2100.
You are right that further urbanization is expected and buying outside of cities may not be a good investment.
Yeah I guess that explains the fond memories part.
Some 32-bit parts are totally flat. Like low-end ARM parts with SRAM and no MMU. Compare that to a 8-bit or 16-bit PIC microcontroller where you need to bank switch to have a usable amount of memory for your application and its heaven.
But yeah, I see what you are saying. Still, pulling the wool over someone's eyes doesn't seem so bad to me about virtual->physical memory and TLBs as it does making them jump through a distinction between pointer types, but maybe I am in the minority on that.
Totally agree. I've been making the same argument elsewhere on this thread. People are disagreeing with saying things were simpler back then. I don't know how anyone can have fond memories of a 16-bit CPU with segments or bank switching compared to a modern flat model and think it was simpler.
It does though, if you mix near and far pointers, you are going to be getting crashes. Pointer equality and comparison are non-trivial. Whereas on a modern 32-bit CPU you don't have any such distinction.
A 16-bit space is not at all simplified, it's far more complex. Because of that, it is a terrible choice. It's a much more difficult memory model to learn in. In a flat 32-bit address space, a pointer is a pointer and it just works. It's much easier to conceptualize and learn on. Have you ever programmed for a bank switched memory computer? It's a nightmare. It's extra mental gymnastics pushed on the developer that have been irrelevant for a long time.
I don't think your example is a valid comparison. It's more like do you think all teenagers need to learn to drive a horse driven carriage before they learn on a modern car?
I remember hearing about these around 2008 and then the application being pushed was no cables to your fancy flat screen TV. Blu-ray player uses UWB RF so no cables are necessary. I don't think anyone saw then the end of physical media and the rise of streaming on the horizon.
I also remember in 2008 hearing about how RFID would soon be ubiquitous on consumer products like UPCs and you could just load up a cart with groceries and walk out the door without scanning anything. That one may actually pan out, but it is much later than it was supposed to be.
Sure you can learn a lot but I have no idea why you would choose Turbo C in 2020 over say a Raspberry Pi with GCC. Turbo C (discontinued in 1990) is going to expose a bunch of irrelevant things today, as even most microcontrollers are 32-bit:
painful 16-bit near/far memory model
a single task operating system (DOS) that has been long obsolete
no support for networking or threads
I could go on and on.
Definitely true.
People also seem to forget the Red River basin (e.g., North Dakota, Minnesota, Manitoba) that flows north to Hudson Bay was a massive lake about 10,000 years ago called Lake Agassiz. So its periodic flood pattern is expected. The topography today is a flat flood plain. Because of the lake bottom history, the soil is extremely fertile. But the cities Fargo, Grand Forks, and Winnipeg are not well placed to avoid flooding. Floods happened in the early 1800s before the arrival of settlements, wetland draining, plowing, etc.
https://en.wikipedia.org/wiki/Lake_Agassiz
https://en.wikipedia.org/wiki/1826_Red_River_flood
...I've done it and it was nothing like that.
Some things are much easier with ODB electronics though. Like if a cylinder is misfiring, you pull out a code scanner and see exactly which spark plug needs to get replaced.
I mean that sounds more like "It's a pain in the ass to change a headlight in my girlfriend's car, so I have her bring it to a shop" than a right to repair issue. Or are you saying the shop needs special tooling to get the job done? What kind of car is it? There's usually a few YouTube videos showing how to do things like this.
I have an older gas guzzling SUV on a truck chassis. Lots of repairs are a lot easier than my wife's car, because there is a lot more space. But that is a fundamental tradeoff between two vehicle classes and gas guzzlers versus high MPG crossovers. My SUV is newer than her car too.
> Can you quickly preserve the food in your fridge/freezer without electricity?
What do you even mean by this?
"The power is out kids! Start a bonfire in the front yard, we're making pemmican and jerky!"
In all seriousness, I've been through a number of multi-day power outages. You leave the door to your fridge/freezer shut as much as possible. When you open it, you make it infrequent and fast. They are well insulated, things stay cold for a long time.
Yes this and it is also much harder to switch off a heavy DC load than an AC one. Once current starts flowing in DC and you try to open a switch, an arc will form that never gets extinguished since the voltage doesn't cross 0 like it does in AC. Hence why switches are always significantly derated for DC versus AC.
If it's publically traded, yeah, nothing nefarious happened. But if it's private, all bets are off. Often, options there are nothing more than a couple of pages of paper tracked by the company itself. It may very well require legal advice to unwind what happened.
I have relatives in the Dakotas who get pissed at traffic lights in general. As in, they live in a county without a single traffic light.
There unfortunately is a very bad habit of some drivers in these areas of blowing stop signs because they are used to so little traffic/people in general. But obviously the consequences can be horrible (see Bill Janklow, ex-South Dakota governor who then later became an ex-con).
Right this minute you could find very fast internet (fiber) in rural areas with very inexpensive housing. I have a relatives in the Dakotas & Nebraska with better internet than I have in Denver. Some of them live in town and some of them live in the country. A lot of it seems to depend on local government having the drive to get rural access funds from the FCC.
As another said, eastern Montana could be brutal if its not something you are used to. There are extremely hot and extremely cold days (in the -30s degrees F) possible. It will be really windy and really brown (its very dry) for much of the year. You might also be shocked by how much some people drink/use other substances and how they get around when incapacitated. (There is no Lyft/Uber). There will not be a lot of young singles around, either.
I personally don't think there will be a big boom because of Starlink for housing. At the end of the day, internet is just a small factor in what makes a place desirable to live. Climate, distance to city/airport, local bars & restaurants, scenic beauty, and local activities all factor a lot, too.
Turbo codes are typically soft decision codes, which don't make a ton of sense at the filesystem level, since there has already been a hard decision made. They are useful in storage at the read channel level, as in processing the analog stream from the head on the hard drive.
Reed-Solomon is often used in storage because it is an optimal erasure code - e.g., I know this block is missing or corrupt, correct it.
Curious - what are your complaints on these programs? My main one is that they are slow to create archives and rsbep only does error decoding, not erasure. I'm working on an alternative tool that is much faster, but curious if you have any other feedback.
This is not true. I have encountered several times on systems with ECC memory where MD5 values for large archives change on magnetic discs. No read errors or SMART errors. I have a HDD (1TB Western Digital Green) in my desk drawer that does this after a couple weeks of cold storage.
Wow! 100g acceleration, Mach 10 in 5 seconds. I can't imagine the level of noise from that.
This same problem also led to the loss of the Deep Impact spacecraft on its extended mission:
"On September 20, 2013, NASA abandoned further attempts to contact the craft.[77] According to chief scientist A'Hearn,[78] the reason for the software malfunction was a Y2K-like problem. August 11, 2013, 00:38:49, was 232 tenth-seconds from January 1, 2000, leading to speculation that a system on the craft tracked time in one-tenth second increments since January 1, 2000, and stored it in an unsigned 32-bit integer, which then overflowed at this time, similar to the Year 2038 problem"
https://en.wikipedia.org/wiki/Deep_Impact_(spacecraft)#Conta...
I've worked with hardware accelerated vector graphics engines (2D GPUs). It sounds like a good idea to do everything vector, because some things are very simple while retaining quality as you said. But in my experience, the vector operations are so expensive compared to raster ones that you go back to rasters to maintain framerate.
The tools aren't much fun on Windows, either.
I've heard e-fuses in general are vulnerable to optical inspection under polarized light after deliding a part. So if someone capable really wanted to clone a device, it's very possible they already were able to get the e-fuse key values.
I once used the e-fuse feature of another part for bootloader integrity. I wasn't worried about encryption, but the part would validate the bootloader integrity when encrypted. If integrity failed, the part would keep searching for a valid image. It was an easy way for some protection against flash corruption.
Sure, but there is no way this should be used as a reference in 2019. It was wrong even in 2003 when it was written - Unicode 3.0 from 1999 defined the maximum number of code points, surrogate pairs, and code points above U+FFFF.
His single most important fact still rings true though, "It does not make sense to have a string without knowing what encoding it uses."
Yeah, I meant don't use it. It seems to confuse things to even bring it up.
I just read this over and it's a very dated Windows-centric view. Several glaring errors - glosses over the difference between UCS-2 and UTF-16, no mention of surrogate pairs for UTF-16 (thinks only 65k code points), says UTF-8 can be up to 6 bytes (no it can't, this was proposed but never standardized), the idea that ASCII standardization dates to the 8088 (its much older), mentions UTF-7 (don't), no mention that wchar_t changes size based on platform, no mention of Han unification, no mention of shaping, and no mention of normalization.
Many Linux utilities do things with the kibi terms, using the MiB, GiB, TiB units.
There have been a few lawsuits about this:
https://en.wikipedia.org/wiki/Binary_prefix#Consumer_confusi...
The outcome is that hard drive manufacturers need to explicitly print their definition of a "gigabyte". IMHO, it's not a right or wrong discussion, just a difference.
I'm not sure in your wife's particular case, but halos are a negative side effect of LASIK in some cases. It is not something that is always there the patient can now see. It has to do with the size of a patient's pupil versus the size of the area that can get corrected. Patients with very large pupils are told not to get the surgery period due to adverse halo effects.