skysight-inc/HackerNews huggingface dataset:
A house is, for most people, a very large transaction. Saying "it isn't that hard" considering attorney's specialize in real estate is like saying "reading x-rays isn't that hard".

Had I not had an attorney present, it would have taken me all day, instead of 4 hours of reading stuff. It wasn't a matter of confidence in myself, it was a matter of having less than 100% trust in everyone else present.
What I like the most is the abstraction-away from plaintext source files. Imagine a C and C++ IDE that hid the (often ugly) source files from you put only exposed individual function definitions - it could automatically keep header files in-sync, for example, and automatically place each free-function or class member in the right file without manual refactoring.

(I still think it's outrageous that C is still a single-pass language - we shouldn't need separate simultaneous declaration and definitions any more)
"Considering that it happens only on Ryzen and with multiple GCC versions and that the first post in this Gentoo forum thread shows segfaults in bash (not gcc) it looks rather like a CPU bug manifesting itself under load.
"

Well, maybe.

x86 is obviously a large target, and there are definitely weird corner cases and stuff that, while often not legal, just happen to work on intel and not amd (or vice versa)

I'd still bet on that before i'd bet on hardware bug.
Certainly the hardware bugs occur, but software tends to be buggier :)
I've really been enjoying reading Brent Simmons blog about his efforts to get Frontier running on modern macOS:

http://inessential.com/frontierdiary

I suppose that Apple Dylan was similar to Frontier in the sense that they were programming environments built around an object databases. Frontier was a shipping product though!
One of my side projects is a music recommendation system. Music brainz has been great for this. Tying together all the music services out there. In addition the biggest perk is you can do a slave of their database, and have it replicate on an interval.
Nigeria’s Afrobeat Music Scene Is Booming, but Profits Go to Pirates
It doesn't really matter when physical media is no longer required or desired. Books, DVDs. CDs and such like are going the way of LP records - quaint, for gifts and decorative purposes. In this brave new world it is how good the gift-item looks on the covfefe table that matters. Even then the book will be migrated out to storage and the charity shop in due course as nobody has space for clutter these days.

What I am disappointed with is how we used to have mostly Penguin Books and their imprints, all with uniform and good looking spines. A wall full of Penguin Books looked awesome. But then we moved to this 'pile em high' retail model where the designers took over the cover designs to jazz them up and make them the bestsellers we know today.
I think I would love this.
It would cease to be Linux, but by all means -- make it so!

BTW Redox OS (written in rust) originally supported Linux syscalls which I thought was a super cool feature.

Jorge Aparicio started steed, a libc implemented in rust for rust. It seems like a pretty interesting approach.
Hm. Font stuff I'm not surprised, fonts can be tricky especially in Latex, you're definitely right. Bit surprised images were difficult. I guess I haven't had to deal much with margin and header issues. fancyhdr can certainly be confusing. Did you try "lyx"? I guess for what it does help with, it might not actually make any of these particular issues easier..

Of course, it's all about using a good template. Usually I find there are tons of resources out there, but it does often involve finding someone with the same problem and asking the right question.
The 10PM Bus
Can blood transfusions from teenagers slow the ageing process?
What happened with the cheering? It's like watching a comedy without the recorded laughter.
It's what you get used to. I'm used to x86 being "dst,src". It never bothered me that on the Motorola 68000 it went "src,dst" as, it was what it was. Intel defined it one way, Motorola another way [1].

My gripe with AT&T style (and it's called AT&T because K&R wrote their assembler that way) is that it uses sigils to mark registers (something I've never seen any other assembler do) and specifically broke with the manufacturer's mnemonics. Yes, I can see why they did it that way (a consistent format for assembly across multiple architectures) but I don't necessarily agree with it (Go's assembler has gone father by not even bothering with the register names the manufacturer uses).

Almost forgot---another annoying aspect of AT&T is the use of "$" to designate an immediate value. Every assembler I used (prior to my exposure to Unix) used "#" for immediate value, and "$" for hexadecimal. But noooo, AT&T had to use "$" for immediate, and "0x" to designate hexadecimal and thus, I hit a brick wall each time I read code in AT&T format.

[1] Also interesting to note---Intel is little endian, Motorola is bigendian.
Here's a nice horizontal one for you :) https://scoutparts.com/products/photos/18520_237275.jpg
> Migration since the 60's has become a giant IQ-sorting system and that's having huge consequences on all sides. And this never seems to get discussed, oddly.

Not in the US, where there is virtually nothing except family-based migration.
America Is Getting a Raise, and Goldman Sachs Is Freaking Out About It
Absolutely, I am personally beating the market on a constant basis, it is actually easier when trading 5,6,7 digits account because of liquidity... but that is not important, the important part is that you can do it too, just test few simple trend following strategies against S&P 500 (symbol SPY) for example and you'll see it clearly...
For safety, the transmitter could turn itself off if a receiver isn't receiving enough power. The receiver could radio back to the transmitter to identify its presence and power input.
No Lisp? :-(
Healthcare. If you ended up paying from pocket.
Back when they actually had an R&D department.
The article covers both of your points:

> Rust is supposed to be an excellent systems programming language, having the ability to go extremely close to the bare metal, while offering a thick layer of security and expressiveness which C lacks of. And such an assumption has to be trialled!

> Which Philipp Oppermann has already done by beginning to write a real OS in Rust and writing about it. But this is not a realistic trial: an OS starting from scratch has almost zero chance to end up being finished, not to mention being actually used on real machines.

That is, a more accurate title might be "Proof of concept of incrementally rewriting the Linux kernel in Rust".
Know more here http://bit.do/Google-removes-SIMD-js
Debatedly, you get a better stdlib and some usability features.
Last 20 years we had 2 times when the market fell in half, and if you are retired to recover from 50% loss, you'll need a 100% gain... why lose money when you can make a killing on the way down? In Japan, the second strongest economy at the time they are still half way down from the top with no recovery in sight and a lot of retirees loosing their savings in the process of "buy and hope trading strategy"
I have a 2003 Pilot with 250k miles. It will die someday, but it's lasted about 5 years longer than I expected it so far!
Macintosh Common Lisp is another one. It was so much fun to use and worked so well with MacOS. Echoing etchalon's comment, sometimes I miss OS 8 (also 9).

https://en.wikipedia.org/wiki/Macintosh_Common_Lisp
Hmm. Convenience is the exact reason I'd give for staying away from "a lot of messaging apps" and using primarily SMS. I've got a couple friends that really like Signal, so that's the only other messaging app I ever install.
The problem I always thought there was with the Mars colony stuff was that there's too little infrastructure on the way, and going straight from Earth surface to Mars surface with essentially no infrastructure in between is a recipe for expensive disaster. We have 3 expensive and difficult steps between the two - Earth surface to orbit, Earth orbit to Mars orbit, and Mars orbit to Mars surface. If anything goes wrong anywhere, it's almost impossible to fix or send help when it can only come from Earth Surface.

It's hard to figure anyone being motivated to build much infrastructure in Mars orbit, so I'd like to see some real infrastructure in Earth orbit. Meaning hundreds of semi-permanent residents, rotation for artificial gravity, capturing asteroids and comets to have bulk raw material, setting up some limited manufacturing there of pure space craft. All in a place where help from or escape to Earth is fast and relatively easy. Get to where sending a colony fleet to Mars is a modest stretch of existing capabilities, not a wild reach involving inventing dozens of new fields.
Yes, absolutely, I just read it earlier :-)
> I doubt phone companies let people directly send voicemail to people as they wouldn't be billing for that.

I mean- they could just bill for that. Like, offer a product that would send a voicemail message directly. Evil but I would not put it past a cell carrier.
You can't get unsecured credit that cheap for very long or in great quantities.

And when people do shit like that with home equity loans, etc, everything works great until it doesn't.
I think you mean the Hobbit, which was mentioned in parent comment. People didn't like it because they are so used to blurry low frame rate movies. If all movies were filmed like that, people would quickly get used to it. Soon they wouldn't be able to stand 24 fps. It's objectively worse.

Similarly footage shot with digital cameras is often modified to look more like film. There's no objective reason for it most of the time, people are just used to the artifacts of film. Anything else "looks weird". Now stuff like lens flare, shaky cameras, etc, are added to shots made entirely in CG!

I can get past that stuff because it doesn't make the quality that much worse, but low fps definitely does. What's the point of having super high resolution 4k display, if the scenes displayed on it are incredibly blurry from a low frame rate?
Somewhat related - are there similar resources for other other kinds of software?
Productivity is not writing more code, but rather finishing more work, and while there's an overlap, they're substantially different things.

If you are taking less time than the rest, there are a couple of possibilities:

- You are a legit virtuoso of software. <- this is possible, but less likely.

- You are cutting corners and leaving work for others to do. <- this is much more likely

In the first case there's no problem. In the second case you are not truly finishing your work and the team has a legitimate reason to ask you to finish your leftover work.

If everyone starts contributing code leaving left-overs to inflate their productivity, it quickly becomes a race to the bottom: technical bankruptcy.

If you are not able to explain what your code does word by word that means for a start that you did not read the documentation, you repurposed code you don't really understand. Therefore your time savings are at the expense of compromising the quality.

If you didn't handle errors, if you didn't write tests, if you hardcoded magic numbers and strings, if you didn't test your code, if you didn't stick to the coding standard, if your identifiers don't reflect the code they represent, if you coupled unrelated code and performed actions at a distance... you are also saving time at the expense of the product quality because you cheated to finish earlier. All those problems add up to technical debt.
Is Renewable Energy Killing Coal, Nuclear, and Grid Reliability?
The Microarchitecture of Intel, AMD and VIA CPUs [pdf]
Agner Fog's microarchitecture document has been updated for AMD Ryzen.
I once heard a professor talk about writing a book 30 or so years ago. He looked at all the available options and decided latex wasn't perfect, but was the best available. 20 years later he decided to look at everything again and was appalled that latex was still the best option he had.

Have you ever tried to color a latex table? If you color a cell, most readers will cover ~1 pixel of the upper and left table borders with the cell color, regardless of the zoom level. This is especially a problem on zoom levels where the border is only 1 or 2 pixels, but makes you feel insane when you zoom in so it's 10 or more. You know what the most common advice for fixing this is? "Get rid of your table borders. It will make your table look better."

Latex is full of little problems like this, but it's still the best.
It looks like this will prevent attacks that use information leakage to figure out valid addresses. With ASLR, you can defeat it if you can get the target to send a return address or other code pointer back to you, because you'll then be able to see where the code is loaded. With this, a pointer to code is likely useless: the authentication code depends on the target address, so you wouldn't be able to forge a valid pointer to a different address, and it depends on the current stack pointer, so you wouldn't even be able to reuse the value to point to the same address unless you found an exploit with the exact same stack depth.
A CL Common Lisp and Racket are included.
This is great and all except I had registered the company I work for to be on the private beta, and have not heard anything for weeks. There's not even a place or number or email to contact, it's just a Google Form. I even signed up for their Brillo/Weave program (now Android Things), and also heard nothing back. You either have to have some internal connection to get any attention or just wait for their service to go into production, which is God knows when.
If you set `conceallevel' to 2 and use syntax highlighting, you should get it in vim without any plugins needed (although I have only neovim installed).

For example, \AA -> Å, $\pm$ -> ±, and {\'e} -> é.

http://vimdoc.sourceforge.net/htmldoc/syntax.html#tex-concea...
I think the deal is that you can't create a good address using the upper bits of a good one ...

It's not the misses you worry about, it's the hits
How would they understand the original icons, then? Nobody I asked understood them, except for the "kcal" icon which you would only understand if you could read.

McDonald's plan to get people to understand them is to put the words next to the icons to get people to understand the icons, which also wouldn't help if you can't read.
It's exactly the same with letters. There's nothing particularly evocative about the English 'a' in the glyph for it.

Even the arrows the OP mentions is learned association.
This does raise the question: which languages other than AT&T assembly put the value first?
Alternatives to US cloud services for developers
Voicemail is just another tool for communication. It allows for one way communication towards you, which might be useless in most cases but indispensable in some.

If you are someone who conducts a lot of business over the phone, voicemail is a must. If someone "important" is trying to call you / get hold of you and you are unavailable, your default goal should be to "reduce friction" for the other person to get the message to you! ("important" usually means they are really busy and they value their time a lot, and you should too.... Clients, Board, Investors, Counsel, Accountant, your managers, doctor, etc... ). Having voicemail disabled and requiring people to text you or email you after having tried to call you (which usually means it's time sensitive / important-ish) is adding more friction/resistance in the communications line. It also comes off as very unprofessional. What if you don't have their number saved on your phone or they call from an unknown number and you don't know who the miss call is from...adds a lot of lag in the communication pipeline.

Voicemail also allows you to take your time in getting back to someone if you don't want to / can't have a conversation right away, but you want to know what they might want to talk about. You can then prepare for the topic and call back.

My iPhone does a decent job at converting voicemail-to-text (at&t visual voicemail). I can quickly scroll through my voicemails, delete stuff from marketers/advertisements and call back important ones after reading/listening to the message. Voicemail has definitely help me prepare for important call-back more than a few times (especially while dealing with general counsel).

I would never disable my voicemail or let my inbox get full (voicemail inboxes filling up might be a "thing of the past" very soon!)
Grand Central Station handles close to three times the number of passengers that the busiest airport in the world handles while taking up less than a third of the land area.
I remember telling my parents this was my favorite book when I was 10. I'm currently reading the Chinese translation since it matches my current Chinese reading level, and it's been quite enjoyable, even though a lot of English-specific word play is lost in translation.
MIT issues statement regarding research on Paris Agreement
Well...

1. You asserted that 0/0% in image codecs was superblack. The most common codec for which that is actually true is WebP, which I'll bet no one in this thread actually cares about.

2. In digital colorimetry, gamut and range are orthogonal. Gamut is the space of real colors a given colorspace encompasses, range is whether the digital signal is quantized to 85% of the theoretical bitdepth and is what we've been talking about. Rec 2020 very much does increase gamut, as mentioned in your link.

3. Studios are actually starting to master in full-range 48-bit RGB (or XYZ technically, I think...) But yeah, that's irrelevant to end-users and this discussion.

4. Yes, everyone has been talking about PCs and how they render / output to TVs. That's why images and MPC were mentioned; broadcast doesn't deal with images. Computers deal with full-range RGB; that's literally the framebuffer format everyone renders everything to. As such, they convert video's YCbCr to full-range RGB before HDMI or TVs come into the picture; MPC's setting mentioned earlier is to ignore what the file says about its YCbCr range when it performs that conversion. Because while there are video files on the internet that set the wrong range, there are also internet video files that are legitimately full-range. And I'm not even talking about ancient codecs using palettes or VQ.

And since computers have traditionally outputted full-range digital RGB signals (over DVI, DisplayPort, LVDS, etc), they do indeed negotiate full-range RGB over HDMI when possible. And yes, even $200 TVs generally support that nowadays.

Heck, if you created a full-range H.264 file, tossed it on a thumb drive, and stuck it in your TV, I'd be willing to bet most if not all modern TVs play it correctly.
Wow, I expected Erlang to score better, considering the claims of Elixir community how fast it is... compared to Ruby. OTOH maybe that tells more about Ruby.
It sounds like the virtual equivalent of putting a slot machine in your lobby with a sign stating "gambling prohibited" next to it.
People tell me it's as readable as Python, has macros, compiles to efficient C (among others), and is easier to learn than Rust esp since it's GC'd. These are good reasons to use it for many apps. I put it in Go's category mostly. However, I think affine types (Rust's advantage) could be added to it or a safety-critical subset.
advice that a lot of founders will listen to because they often assume a VC knows what they're talking about

Why would people assume that? Maybe I'm weird, but I tend to assume that VC's know a lot about, well, VC, and pretty much squat about anything else. It's like the old saying, "Those who can, do. Those who can't, invest". OK, so that's not the original saying, but I'd assume anybody who knows anything about building a real business would rather spend their time building a business, not just investing and sitting on the sidelines acting as an "advisor".
I ended up doing that for the netcode.io port of Rust and it worked out really well. Both in stubbing out implementations and in calling C API from Rust until I had 100% Rust implementation.
I'd argue that Safari was one of the biggest things that sold me on the platform, before the app store.

At the time I had a Windows Mobile 6 phone and while there was a lot of great things about it, Safari's browser experience - even on iOS 2 - was revolutionary.

It absolutely blew the alternatives out of the park.
Rust doesn't have downsides of C++ by design.
Unfortunately, preprocessing would make this difficult or impossible. Even with modern C++, people still rely on it.
I've typeset novels, technical manuals, math, poetry, articles, chess diagrams, posters, presentations, my resume, and probably a bunch of other things in LaTeX. It wasn't a big deal, though it's definitely a rabbit hole in terms of the amount of tweaking that's required if you want everything just right, if you're doing something fancy, and if what you're doing doesn't quite fit any of the many pre-written templates. The great thing, though, is that once you've tweaked one document the way you like it, now you've got a template to use for documents of the same type, which should only require minor tweaking in the future.

There's definitely a learning curve to LaTeX, but not a huge one, as it's mostly just a markup language. If you want to get in to the programming side of it, or if you want to learn one of the larger LaTeX packages really well, that would take you more time, but not even then it shouldn't scare anyone, particularly if you've learned other high level programming languages before. Diving in to TeX itself could be a different story, but I can't comment since I've never bothered to learn it myself, and haven't had to for anything that I've done with LaTeX.
Look up the names Schwartz and Aurenheimer. They either ignored the click through EULA or deliberately broke it. Charged with CFAA felonies over it. One got prison for many years. The other killed himself to avoid it as well as to protest the insanity of having criminal charges brought against them because they broke the EULA terms on a web site. Both used scripts to cycle through ID numbers in a web page. This is what happens when you don't read. The system is fucked. Better make sure you aren't violating the TOS on any of the web sites you visit.
This has nothing to do with competence. Competence is not never making mistakes (if somebody tells you he never makes mistakes, it's actually more likely he's just incompetent enough to not notice them). Competence is arranging work in a way that mistakes don't result in a disaster. Which clearly wasn't the job of the junior dude, and very likely was the job of the CTO. I could easily count at least half-dozen ways in the situation was a total fail before the mistake happened.
So no, one shouldn't be given free pass for mistakes. But one should expect mistakes to happen and deal with them as facts of life.
As for killing whole prod database, anybody who have spent some good time in ops/devops/etc. has war stories like this. Dropping wrong instance, wiping wrong system, disabling network on wrong system... A lot of people been there and done that. If it didn't happen to you yet and you're in the line of work where it can - it will. It would feel awful too. But it'll pass and you'd be smarter for it.
What 600-page documentation are you referring to? The TeXbook by Knuth goes only up to page 483 (with the appendixes starting on page 304).

By the way, a really excellent book for (plain) TeX is A Beginner's Book of TeX by Seroul and Levy: it's truly for the beginner, yet at the end you'll be practically an expert, or at least know how to become one.

I've seen people get frustrated with LaTeX (not TeX), but that's because it was designed to make it difficult to do typesetting: instead the LaTeX philosophy is to specify only the document structure, and leave all the typesetting to a package that you hope someone has written.