skysight-inc/HackerNews huggingface dataset:
I'd be fine with having another GPU, but the problem for me is that as I understand that would mean that only Ableton can be on that monitor. I'm just a music hobbyist and I like to switch between web browser/vlc/whatever and Ableton while I'm just screwing around. That was one of the reason I didn't really want to dual boot. I'm not just entirely focused on Ableton, I just muck around for fun while I'm doing other stuff.

Can you have a separate GPU doing the graphics processing for a VM in a window on a different GPU? Hope I explained that ok.

What I'd like ideally is to have my cake and eat it too - to be able to run Ubuntu, but have Ableton running just like a native window - so I can move it to any monitor, minimize it, etc. Of course if that's not possible then that's the way it is and I have to accept it.

Another problem I'm thinking about is that I won't be able to passthrough the soundcard to Windows and still have sound coming out of it from Ubuntu - so I'd need to use a second soundcard and then have a mixer to combine their outputs!
Is anyone using Mongo in a large volume production system?
Top priorities for documentation: how to set up a production environment; how to get up a working copy running from scratch; any arcane command-line incantations or click sequences that you have to look up (or worse, work out by trial and error) more than twice. Document these from the get-go. In an emergency you’ll be glad you have them, and the next person you onboard will be grateful.

Second level priorities: complex algorithms; counterintuitive design decisions; complex high-level business logic, especially logic that’s spread across multiple methods/classes/modules. These are useful even for a solo developer if you end up stepping away from that area of the code for more than a month at a time. Once your team is big enough that people are regularly editing parts of the codebase that someone else wrote (or that depend on code someone else wrote) having this can save you hours of developer time per week.

Middling priority: documentation for HTTP APIs (and any other inter-process communication APIs). If you can auto-generate as much of this as possible, do so. I haven’t found it useful enough to put time into writing manually for a team of <15, but this is also on the hours per week list if the people consuming the APIs weren’t involved in writing or designing them.

Lowest priority: doc blocks and internal API documentation. Generally your developers can work this stuff out on their own. Depending on your language, API docs with function signatures may be auto-generatable, though the utility is limited if your developers are already using IDEs and other tools that provide autocomplete and lookups. Doc blocks with function descriptions are useful if the function does something unintuitive or too complex to be described in the name and should be written as part of general commenting practice as a matter of course.
Inmutability of the transaction history.
In the early 80's I started on a Commodore with a BASIC interpreter "command line," spent a few years later learning DOS, and did not encounter UNIX until about '93 when a teacher mentioned Minix as a way to learn it. At work I installed Slackware from floppies, and was exposed to Sun/SGI/and VAX, good times. Took to each like a duck to water. Liked GUIs and GUI programming as well.

Never understood the folks that wanted to only use one or the other, not both, when they are complimentary. Avoiding either is doing yourself a disservice.
Ubuntu, with default configuration, does create new user directories as globally-readable, but that's just a poor security decision on their part. There's nothing special about /home itself; it's just the default behavior of adduser. And the permissions on /home have no effect on what the permissions are on new subdirectories created when a user is added.
Is it me or anyone read this "1MDB" as IMDB?
This is the real problem. If the consumer price is $50 but the insurer is paying $250 behind the scenes, then we all pay that price with increased premiums.
I think they only pointed out that he improves relative to his opponent.
Irrelevant tangent: I was in Albert Heijn (common Dutch supermarket) today, the one in Amsterdam at Dam Square. They recently sell "Danish Chef Cheese Spread" (you might imagine Cheez Whiz in a tube), which I'm addicted to, to the detriment of my health. As I was stuffing tubes of this into my basket, a pretty young Chinese woman (tourist) stood right beside me and said something in Chinese. It took me a few seconds to realize she'd spoken Chinese and couldn't care less if I existed. It so happens that, at the risk of humble-bragging, I've taken some Chinese lessons. Ten more seconds later, I understood what she'd said: zhe shi shenme? "What is this?" She had no idea what this bin of cheese tubes was, and why would she? I then spent another half-minute trying to think of the word for "cheese" in Chinese. Of course, I was too late, and she re-joined several other attractive Chinese people. Google translate says Qǐ sī (chee suh), but is that possibly the actual translation? I may never know.
> "If you're chasing pointers without being sure that it points to a valid address, you're doing it wrong". Well, perhaps so, but in practice lots of programs were doing it wrong, and it was the users who suffered.

Except ".." also is a solution to permitting you to traverse a directory tree without accidentally chasing an invalid pointer; no bug in your program nor any external application can ever make ".." invalid. ".." is equivalent to a back pointer in a linked list or tree structure. Imagine you have a handle to /foo/bar/baz and want to ascend to baz's parent. Between acquiring the handle to /foo/bar/baz and attempting to ascend to the parent, "baz" could have been moved and "/foo/bar" may not exist. Without ".." all of a sudden you're orphaned and your application is stuck in an inconsistent state. Maybe the best solution is to just panic, but that's like saying that all applications should be prepared for any pointer access to segfault at at any moment. That's one solution, and it's actually how some smartphone application environments work. Another solution is guaranteeing the condition can't happen, period. Which is preferable depends on your use cases and which side of an interface you'd prefer to place the burden. For pointers it's fairly obvious which provides the most preferable semantics for maximum safety (or it was until the smartphone and cloud paradigms), but for file systems the answer is less obvious. In Unix when ascending directory trees the scenario of a valid pointer becoming invalid is impossible such that there's always a valid path to the root of the tree (even if the depth can change; you just stop when opening ".." simply reopens the same directory), but for descent there remains the race between readdir + open (as opposed to readdir atomically returning file handles).

These particular semantics were clearly purposeful, not an accident. The former was thought useful, the latter an acceptable simplification. It's why in Unix you can't delete a populated directory in or when a process holds an open reference (unlike other file types), and why you can't hardlink directories.
Global surveillance disclosures (2013–present)
I think "at the time of writing" implies they're still under consideration, rather than outright rejected due to philosophical differences.
I'm an iOS dev and I would potentially be interested in contributing. I can email you later if you'd like (I see your email is in your profile).
If this kind of ala-carte plan is interesting to you, check out ting. very similar but lower price. works with cdma or gsm phones.

https://ting.com
Cool. I don't think I've ever heard a war story about a SmallTalk codebase before -- I have always gotten the impression that SmallTalk was a research/toy language similar to Haskell that is held in high regard but rarely used in production.
I think it's pretty dependent on your application strategy. Some people are fairly R-selected in their strategy. Large number of applications, but little customization of resumes for each job and no cover letter. Others are more k selected, they'll write good cover letters and change up their resume to better highlight relevant experience.
I know some professional translators who specialize in cleaning up machine-generated translations so that they have that 'native speaker' quality (Yes, including DeepL). I doubt Amazon Translate will help that much, if the goal is to reduce the use of a native speaker to clean up the generated translation.
> No, globals like that are very problematic

Indeed, they're terrible. What I don't understand is why basically every Google-authored project has loads of these (protobuf, gflags, TensorFlow...)
That explains why there are a lot of Amazon postings on the site, not why the mentioned account is exclusively used to promote Amazon announcements.
Very fair point, but only from one perspective. Yeah I gave them my money, but they did have to pay at least 4 hours or salary+benefits for at least one person just talking to me on the phone. That doesn't include anyone else behind the scenes who was used to help rectify the issue from the technical side. Nor does it include the cost of however many other people also encounter these issues and have to spend inordinate amounts of time on the phone with their employees. That can easily add up.
Property values are tied to school ratings and crime statistics.
Mostly because being POSIX compliant makes it far easier to port a lot of command-line and server-side software quickly. Most new operating system projects don’t have the manpower to rewrite the world - I think the last major one was probably Android.
Nobody is proposing a non-standard language, that's the point. Literally the entire reason for having a coding standard is to have a well-defined subset of the language you're using.

Meanwhile, the "trouble" the reddit thread comes up with is copy/paste programming for #ifdef. That's a one-time effort of writing a commit hook that checks for that. But no amount of effort will ensure the next compiler you need supports #pragma once
The church encoding goes a lot further than that encoding conditionals and booleans and much more.
One problem is that many people fail to make that distinction and then cargo cult whatever google puts forth for style guides

People need to remember that just because Google does something one way does not imply it is correct nor that it is incorrect
Also... there is a proposal to fix the overhead of the code that current compilers generate for exception based code.

P0709 R0 – Zero-overhead deterministic exceptions

http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p070...
1000ms hydration may be a big deal, hydration may also take more than 1000ms.
For the record, I use VS Code, but the fastest way to _open_ VS Code is

cd project-name
code .

It also lets me type Git commands directly into the terminal, which is way faster than doing it through VS Code. And there are still plenty of things, like rebasing, which VS Code doesn't have GUI support for.
Check out Music Transformer that was recently published
https://arxiv.org/abs/1809.04281

Some generated samples:
https://storage.googleapis.com/music-transformer/index.html
DinSync RE-303 is probably the most impressive. As they say "it's not a clone it's a replica". They painstakingly traced the PCB, used as much original parts as possible, and you can use the original TB-303 CPU to control it (or you can get the RE-303 CPU with their own firmware since the original is proprietary and long since out of production). Meaning you can use the project to revive a real 303 if you have to, or build your own legit 303.
it is also less bugprone in the real world. There are cases where it doesn't work, but they amount to stupid things that nobody does outside of contrived examples.

I switched our codebase after finding several variations of
#ifdef message_h
#define massage_h
That potential bug existed in our code base for years (I checked history)
That calculation only works if you can spread your workload over ten minutes in the hour. If you want to get it done in ten seconds, then you don’t have any more to do for the next hour, then on-demand is much better.
I did this for the debversion datatype (on pgxn). It's surprisingly easy to create custom types, along with all the necessary operators and hash functions for them to be efficiently indexed and compared. And the speed is excellent, so long as you're using a natively compiled library with the C bindings.

JSONB is clearly a lot more complex and demanding, but if you're ever using PostgreSQL and hitting performance limitations with interpreted languages or PL/pgSQL, it's an option which is not as scary and inaccessible as you might imagine.

CREATE EXTENSION is what really made this stuff usable. Before this, you had to get the user to run a bunch of raw SQL to set all the types and functions, but now it's all wrapped in a single handy SQL statement which can even handle upgrades and uninstallation.

Part of me wants the installation and upgrade mechanism to be reusable for my own application database schemas, it's so convenient and well done.
Correct. That's why people use https://en.wikipedia.org/wiki/F1_score instead of just accuracy.
Group them by topic. “Version control incantations”. “Writing and running tests.” “Debugging.” “Deploys.” “Production troubleshooting.” Etc.
I agree I was simply responding to the question of why so many are there today. Definitely legit to question that particular accounts history.
> Template libraries that have to deal with stuff that could throw vs couldn't end up with lots of nearr duplicate code, twice as much needed test coverage, and/or less efficiency if you just cover the could-throw case. And you will still probably get it wrong.

what are you referring to ? I have never seen template libraries having to do anything particular wrt to exceptions. If you want to throw just throw, that's the point.
There are only 49 million homes in Japan according to Google. 8 million abandoned homes means that almost one in six homes are abandoned. Is that possible?!
My Arch Linux Setup with Gnome 3
Mapgen4
It's a great article. But it's odd that it didn't mention work on our local (fortunately quiet) quasar, Sagittarius A*. Although there's too much dust for visible observations, it's just so damn close. And there's been some great imaging work at gamma, x-ray and radio wavelengths. Although I don't believe that there's a substantial accretion disk, we can actually observe stuff that's orbiting the black hole.
This paper, depending on how you look at it, either justifies the existence of dot dot, or makes it seem like a wart. IMO dot dot is too well-established and essentially sensible (in a minimal UNIX fashion) for it to be removed on a whim. Consider the approach taken by https://man.openbsd.org/unveil.2: if you try to access a file you aren't explicitly allowed to, you get EACCESS or ENOENT. I'm not an expert, and the possibility of errors obviously requires applications to tread more carefully than they might have previously, but it seems like a clean solution.
This is a useful repo for how to structure a Go project: https://github.com/golang-standards/project-layout
Notably with good support for structured logging, which is usually badly supported by log4j descendants (like e.g. Python's logging module).
Microsoft reveals bugs knocked outAzure,Off 362.5 xfa auth logins 4 14 hours
And Elixir's doctests https://elixir-lang.org/getting-started/mix-otp/docs-tests-a...
Japan is not a very good proxy due to their strict immigration policies and preference to be an "ethnically homogeneous nation." As you mentioned, other countries can just replenish their head count through relaxed immigration. I'd wager, for example, that the US will remain highly multicultural with looser immigration long term since it's baked into its identity[0], despite some recent policy changes.

0. https://en.wikipedia.org/wiki/Melting_pot
Grischuk pointed out that according to universal rating system that measures the gap for each category like rapid or blitz and apparently Carlsen is the only one who sometimes gets a negative number on blitz/rapid. Which is most interesting.•

But I agree even so relative to Caruana, whose gaps are much higher. He must have been aware of this.

•http://universalrating.com/ratings.php
I am not a lawyer but aren't NDAs supposed to be protecting information about the company but NOT omitting the fact that you worked there for 9 years? I mean how can someone even ask to not mention 9 years of employment. I am not even sure how you can consider something like that. I am sure severance is not going to be that large right?
Even a qualified appeal to the majority isn't a very good argument. There are many scenarios where the majority of events is caused by a minority of individuals.

For instance, 20% of developers could be responsible for 80% of all software, or 80% of the most used software, or the software that generates 80% of GDP, etc.
and exception-based code can have much less branches since you don't need to check every function call for error but instead let the exception propagate from where they can be thrown. e.g. in a hypothetic case where you load a settings file five layers deep, in an error-code-based solution you have potentially 5 branches while in an exception-based solution you only have one
Talk about a whiplash moment!

GP was talking about critical examination of evidence during the education process. Then you mention public education, as if that provides what GP meant.

How about a politician that makes the distinction between education and schooling? Let's start there.
Ask the financial industry e.g. Swift.
Not finding one. Any volunteers for Rule 35?
Food and energy are not what defines scarcity any more.

If you want to pay the mortgage, have a fulfilling job, have time to spend with your family, and give your child a good start in life, you can't have 8 kids in a middle class family.

Sometimes 1 is the right number if you want your child to be successful and have enough free time to enjoy life yourself.

That IS resource constraint, the resource just isn't food.

The replacement rate is a little above 2 children in the modern world. Three kids is a burden for a lot of people.
Do you have stats on that? I'm not German, so perhaps I'm ill informed, but this report indicates that actual new coal plants have opened up in the past decade.

https://www.energycentral.com/c/ec/why-germanys-nuclear-phas...
Hotels are already cheap in Japan ($60 a night will get you quite a nice business hotel with hot spring in most places I've been) and Airbnb is subject to local restrictions (federal law passed recently allows local governments to place restrictions on Airbnb - you have to get a permission letter from your city Hall to be allowed to list on airbnb - and they can deny you for any reason eg neighbour complaints). Personal use would be a possibility for sure.
In Chromium they are so widespread that makes the rule showing that complex code cannot avoid them and defeating the rule.
You'd never see `v.resize(10, 42);` because 10 and 42 would be in self-documenting variables, e.g.

```

int kDefaultValue = 42;

size_type kExpectedSize = 10;

v.resize(kExpectedSize, kDefaultValue);

```
> The lynchpin of C++ are value-types. Such types should be copyable and moveable and the language automatically generates the necessary constructors and operators by default.

It generates constructors and operators by default. They may not be the ones you want, though. They will satisfy the compiler, but they may do the wrong thing. If the default thing is the right thing, then yes, "= default" makes it obvious. If you don't say, then it isn't obvious whether the default is right, or the default is wrong but you missed it.
That's convoluted... from you example, there are 100K writes/minute, while you assume 1GB data evaluated per minute per alarm. That is you're assuming 10K/item/timeseries for each alarm, while reality is going to be closer to 10-100 bytes/item/time-series, which cuts down the expense by two or three orders of magnitude.
This is the fruition I'm referring to: "could alter the planet". Never seems to be the case.
Since a lot of languages have FFIs for C this made me wonder, did anyone try to write a PostgreSQL extension in... Rust?

Turns out a few people have been working on doing just that.

* JSONDC, a PostgreSQL extension written in Rust. Latest commit about a month ago. 161 commits in total. Authors say “It is written in Rust and, being short, is a good skeleton project for other would be plugin authors who'd like to use Rust to write Postgres extensions”. https://github.com/instructure/jsoncdc

* pgxr. Latest commit 20 days ago. 23 commits in total. “Write PostgreSQL extension functions (as stored procedures) using Rust.”. https://github.com/clia/pgxr

* RPGFFI. Latest commit about a year ago. 33 commits in total. “Imagine being able to create postgresql extensions in rust. We generate bindgen (0.29.1) pg apis for [...]”. https://github.com/posix4e/rpgffi/

* postgres-extension.rs. Latest commit over 2 years ago. 23 commits in total. “Library to write Postgres extensions in Rust! Overall, the Postgres codebase has some pretty narly C macros everywhere, so we have to work around them a little bit.” https://github.com/thehydroimpulse/postgres-extension.rs
Given Live View was only announced two months ago, is in development, and hasn't been released in any form whatsoever, I'm curious as to how you've managed to use it to make that comparison?
Doesn't apply to hard drive and DRAM mfrs (before the last decade of consolidation).
Have you ever written code no one could understand?
Followup from the other thread about inheriting incomprehensible codebases. It's easy to be self-righteous about the poor programming practices of those who came before us, but maybe a little confession would be good too.
Indeed. Still it is the beginning in either case.

With this propulsion technique you potentially break free from the traditional designs and can fly into any given direction.
That's a good way to get _nobody_ operating as a pharmaceutical producer / seller in this country.
In my example the diabetic was passed out. Or like the with diabetics I've had to deal with, stubborn mule-like insistence they're fine! It's the people going into anaphylaxis that I think panic, for pretty good reason.

But it's just an example. My point was more that insulin is generally safer than epinephrine.
This is the part that I wonder about: "And the impact has been very real, and very expensive to mitigate so far."

Is there a good read for the actual impact, if any?
> Lastly, this document reads as if knowing a full path grants access to that path and its subdirectories. If that's the case ... oy.

Well, they speak of the path as a "resource provided to a subprocess". In that context, it sounds more like a handle/file descriptor that the child process can pass to some "read", "write" or "get handles of children" syscalls - and that happens to correspond to the file object at /home/bob/foo.

If so, it wouldn't imply that knowing (or guessing) the string "/home/bob/foo" would automatically give you access to the handle.

That's just my reading of our though, no idea of that is what they actually do.
thanks for all of your suggestions. What do you find is the best way to organize the command-line incantations (what a great way to describe them) and click sequences? do you write them in something like google docs or confluence or in your code?
He made a >joke< that maybe Carlsen should have a negative gap.
Assuming no bad actors what’s the difference between this and a single DB that simply tracks the banana?

A blockchain won’t solve the problem of creating a unique identifier for each banana and ensuring it was correctly scanned.

Also this isn’t a good example fundamentally because the banana is not immutable as in anyone can swap the barcode from one banana with another or it can fall off.

Blockchains really only work when everything is immutable.