skysight-inc/HackerNews huggingface dataset:
He also complains about a Chrome bug, a Slack bug, and an IntilliJ bug. 3rd parties doing no QA and not respecting UX conventions on the most popular distro is a problem, but not really with Linux.
City Street Orientations Around the World
I use Control+S,Z,X,C for debugging, mapping Caps Lock to Control. (S=continue, Z=Step Over, X=Step In, C=Step Out). It keeps my right hand free for mousing around, drinking coffee, etc.

What modifier are you using for the arrow keys? Aren't they all taken already?
Big booty Brazilians facesitting
answer your question for those of us trying to make $150k, thanks.
Blockchain Security 101
UPDATE: I over looked the spec part with their Intel chips... however I presume they tie directly into the T2 chip, and will probably leave them altogether in an iteration or two.

As I predicted in a former post on why they haven't updated their hardware line up... "using their T2 chip..."

This is them leaving their dependency and insecurity of Intel and AMD.

Good luck to them. I do remember a time when their ARM G series CPU's out performed x86 cpus on all things creative.
You're right, that did limit enfranchisement. That was gone well before the Civil War, though. That would be an unusual definition of aristocracy, but I get it. By the same token, we currently limit the vote to people over 18 that are citizens. Are we currently aristocrats?
I usually have a half dozen windows of Sublime Text open, but I still occasionally launch Notepad to hold some temporary throwaway text, even though there's no need to.

For some reason I just like having something different open for that "scratch data" that also is visibly differentiated in my taskbar.
duplicate, please check before submitting: https://news.ycombinator.com/item?id=17512175
I can easily ignore iOS and macOS updates for as long as I choose. Windows 10 will forcibly update me on shutdown unless I yank the power. Microsoft takes a much more forceful stance.
One of the notes on the ESLint postmortem[1] was that developers shouldn't reuse passwords and should use a password manager to facilitate making this easier.

While I ack that 2FA would have prevented this incident, so would have using unique credentials. Note that using unique credentials is available at every SaaS service, not just the ones that support 2FA.

[1] https://eslint.org/blog/2018/07/postmortem-for-malicious-pac...
Yeah I understand there are different 'implementations'. But I've seen the same in a totally different company. Work was split vertically, each employee was responsible for handling from a to z. It had issues but it wasn't chaotic. Then consultants came with horizontal decoupling. We were all devoted to a piece of the task, and then nobody knew what the hell was going on. Things were bouncing back and forth. It's nobody's job since you "talked" to the kiosk and employees aren't there to give you something. It's not a restaurant, it's a badly designed factory.
I think devops was defunct once the asphalt hit the hardpan.
Approaching 'generic' secure operational environments as programmable, iterable and contained is one of the great IT lies of the last 20 years.
> And having undefined behaviour in your C code is definitely not a good thing, even if it is basically unavoidable.

If it's literally unavoidable, then the language specification is BROKEN.

Now, most C UB is avoidable, but it's very difficult to notice some UB, and most compilers aren't that good at telling you about the UB they exploit. In this sense UB is unavoidable in that human programmers may often write code with UB without noticing.

If it's only "practically unavoidable", not literally, then the language specification and/or the compilers (by failing to warn about it) are BROKEN.

You cannot blame C programmers, not anymore. The committee has been much too aggressive in its zeal to speed up C by adding more UB cases. We've reached the point where compiler outputs run very fast because all the important bits have been elided by the optimizer, breaking the program in the process. We, the users of the language, have been pushed to the breaking point by the committee and the compiler groups. Please stop. And don't just stop, revisit some of the worst UB decisions.

Yes, even C89 had lots of footguns, but UB was much more manageable.

The only reasons I myself have not yet abandoned C are: a) I haven't learned Rust yet, b) many codebases I work with are C codebases and won't get rewritten in Rust anytime soon, c) it takes time to get enough critical mass. (c) is happening though, and (a) is, for me, just a matter of time; (b) I can solve by moving on to new things, but the world is full of legacy code that we can't just abandon/rewrite, so moving on isn't exactly likely.
And this is exactly why I use Azure: for some very specific tasks, they rock! Just make sure to benchmark everything

Unlike on AWS, I haven't had some service "not available" within a zone (hint: try to get a Lightsail in Brasil) and DNS is not so bad.

I am eargerly waiting for Azure new DC in Africa, hopefully this year.
oh god, their plan might be identical to that for their Windows 10 Solitaire

you either pay a monthly subscription or you get ads

https://images.techhive.com/images/article/2015/07/windows-1...
This seems like an actual upgrade for users still on 2013/14 hardware. Going from dual core to quad core for the 13" users sounds like it might actually be time to upgrade. The benefits of the 15" sound very compelling compared to the 13" tho!
They wont merge the pr unless FreeBSD is added to their CI infrastructure so it's properly supported. But the electron team doesn't want to do the work of adding FreeBSD to their CI. It puts FreeBSD in a catch 22 because either the electron team needs to allow access to the CI infrastructure to a few FreeBSD devs so they can do the work or the Electron team needs to do the work.
Are people disapproving of my experience or that I'm talking about it?
I don't think the explanation killed the joke. As someone who wouldn't have gotten it otherwise, it made me able to appreciate the pun.
You don't have to run with 4 DIMMs but you'll run slower if you do; it's kinda like having a one lane road vs a 4 lane road, you can put all your traffic through one lane, but it's a whole lot slower than using four lanes.
not hot pages, just cache lines
U.S. Justice Department to Appeal Approval of AT&T Acquisition of Time Warner
Ha! That definitely took me a second...
If open floor plans are as beneficial as managent says, then why do they always get to keep their private offices?
Number Identification through primes
It looks like Privacy.com is build on top of Plaid.com for handling the backend ACH processing. Plaid.com exposes a ton of personal information to its customers like Income, Assets, and Employment Verification. What is the scope of your engagement with Plaid?

Do you recommend that users should protect themselves from Plaid.com personal data harvesting by setting up a secondary checking account to use with Privacy.com that is trickle-fed from a primary checking account?
Found some more details here: https://www.postgresql.org/message-id/50E4AAB1.9040902@optio...
I think gigs are ill suited to child care and home cleaning. One bad apple can ruin your life, so you should be super cautious when hiring. We have had the same nanny and the same cleaner for 2+ years.

Price should not be the main factor. Minimizing risk of getting a bad apple is the most important thing, and this is not well done by the current batch of gig apps. Gigs optimize labour fluidity, which is the opposite of what you want.
Because notepad is meant to be... a notepad, not a full blown text editor.
I appreciate the choice myself, but PSA, my impression [0] is even when we consciously think we don't want to talk to anyone, simple human interactions, even with service workers, actually DO raise our base mood/happiness a non-trivial amount.

[0] https://verybadwizards.fireside.fm/136
Note that NPM claims they already disabled NPM access tokens that were used during the timeframe they assigned to this incident so if you were affected, your token was already revoked.

Also, ESLint's postmortem[1] suggests this was password reuse (matching a creds from a previously popped service) + lack of 2FA. In short, a failure of a developer with publish permissions to use basic security hygiene.

[1] https://eslint.org/blog/2018/07/postmortem-for-malicious-pac...
I don't usually repost the same comment from one story to the next, but this might be helpful...

Here's how I checked my own machine, though I was already confident I wouldn't be affected:

find ~ -name eslint-scope -exec grep -H version '{}/package.json' \;

If you use yarn exclusively, this will also work:

yarn cache list | grep eslint-scope-3.7.2
Cargo packages can also execute arbitrary code at compile-time through build scripts, which run with full permissions of the original `cargo` command including filesystem and network access.
> upgrades requiring random restarts completely interrupting my workflow

You'll never see that time again.
It's not just the building part. If it ships with Windows, Microsoft needs to support it for a very long time.
Similar experience to being a hacker-cracker 20 yrs ago, bouncing off servers around the world over a modem connection to telnet into some poor SunOS 4 boxes in South Korea or at GSFC (NASA). Sometimes you had to wait minutes before anything appeared on the screen while TCP was doing its thing. God forbid if you accidentally (yp)cat’d some large file..:)
The Sets feature linked in the article sounds more interesting. https://www.theverge.com/2018/6/27/17510344/microsoft-window...
Microsoft more or less destroyed the competitive market for computer operating systems and office software, and they did it not by producing a superior product, but by using their market power to destroy any potential competitors before they could reach a significant enough market segment to become a threat. What they did was illegal [1], but the deleterious effects of their illegal actions have never been fully remedied. As a result, we now live in a world where we have to live with inferior software produced by a non-competitive market, and the people who broke the law to make this happen are billionaires.

Does that help make it clearer?

(P.S. You probably would have gotten less hate from the downvote brigade if you'd just asked me that in the first place.)

---

[1] https://en.wikipedia.org/wiki/United_States_v._Microsoft_Cor....
This is very much a theme in the Warhammer 40k universe. Tech priests "pray to the Omnissiah" while applying various sacred ointments (lubrication for parts?) to machinery and such to get tech to work [1].

[1] http://warhammer40k.wikia.com/wiki/Tech-Priest
"Antioco was, in fact, a very competent executive—many considered him a retail genius"...yet he made incredibly obvious mistakes to prop up a business with a flawed business model. I fail to see any of the genius, he seems like another corporate idiot in a suit, to me.
I thought Toys-R-Us went under because private equity firms that bought it stood to make more money that way. Probably if it had remained an independent company it would still be around.

https://theweek.com/articles/761124/how-vulture-capitalists-...

https://www.theatlantic.com/magazine/archive/2018/07/toys-r-...
Aliasing rules, for example, have nothing to do with ISAs. Neither do pointer comparison rules, and many others besides.

The rule about memcmp() with invalid pointers by length zero does have to do with actual systems, but it can still be standardized and the vendors with now-non-compliant memcmp() implementations just have to fix it. This has happened before (e.g., snprintf()), so the ISA thing is a total cop-out.
You mean what to replace the democracy with, or the corruption?
Centralized systems can only handle so much complexity before the collapse. You can only handle the kind of society we have today through a distributed, decentralized model. The complexity of modern society is emergent, not the result of central planners. This is a foundational finding of economics and one of the primary reasons why communist dictatorships tend to fail to function.
Check Costco. I bought an XPS 15 with 32gb ram for 1800 last winter.
Live Object Programming in Pharo Mooc – 3rd Run Fall 2018
1. Find a company or startup that desperately needs someone with your skillset ASAP

2. Negotiate hard

3. Have a good reputation
Jusr amoment ago learned about mosh.org that sounds like would be helpful for that kind of situations.
This is side stepping the answer you're looking for: can you change locations with your current salary? The net effect could be living as if you had $250k.

Otherwise, the best way I think reaching beyond the $150k/year salary as a SWE besides becoming a senior Engineer at Google etc. is creating your own startup and keeping the head count small, e.g. like many of the people on Indie Hackers. Of course, I haven't done this yet myself, but that's what I've come to when thinking about this.

Other options I haven't explored as much could be investments of some kind (crypto? traditional stock market? real estate?)
Software getting recreated, sometimes without the security promises (linux containers as they started vs. solaris zones) the previous solution had. To be fair, Google didn't really need the security in linux containers, they didn't run multi-tenant workloads, so it wasn't their top concern when submitting code to the linux kernel...

We like building new things, from different angles, but in the end it seems like everything cycles through the same ideas.
An introduction to friction logging
I think regular CT already causes cancer in ~1/2000 uses. So 10x that dose would probably cause cancer in ~1/200 uses? That's pretty scary.
Not necessarily "better" governance, because that's very dependent on what "better" means to you. I think you can make a strong argument that federalism results in governance more closely matching the will of the people — to the extent that the will of the people can be captured by representative democracy.
It wouldn't play on Firefox. I'll try again and give you my browser specs.

Edit: works on Firefox mobile. Gonna try desktop in a second.
> You pay for any software product you use by not using an alternative.

Sure, but in the same sense "you pay" for eating a day-old egg salad sandwich you found sitting on a park bench. (Luckily, even using badly-written open source software generally has a less unpleasant outcome.)

Like open source, the chef -- who you have no relationship, connection or contract with -- is not under any obligation to guarantee either your satisfaction or survival.

If you want to reduce the risk to your livelihood, you should pay money for both your critical open source software and your egg salad sandwiches.
Just to clarify, you're in the Bay Area or somewhere else?
Yeah if you set frame-src to something that doesn’t include the current domain then it should prevent loading an iframe from the same origin

That being said, this technique might still work in theory on whatever domains you have specified in frame-src if it doesn’t include ‘self’.

So if you’re foo.com and frame-src only allows bar.com. If you managed to get script into foo.com maybe you could put an iframe pointing to bar.com/reallylongorinvalid

That being said I haven’t had a chance to try this out on my machine yet so I could be missing something

Also it looks like their demo includes sandbox allow-same-origin and allow-scripts in its CSP.
Excluding the 2/3 debacle, Guido has overseen an incredible progression in Python. It has become a contemporary lingua franca for coding, and the concept of a “pythonic” approach has been hugely influential.

I’m disappointed that he broke Eric Raymond’s rule: “When you lose interest in a program, your last duty to it is to hand it off to a competent successor.”

The email sounds bitter, which is tremendously sad, and I hope that after a break Guido will be able to oversee a more constructive transition.
Its the infinity fabric. AMD EPYC doesn't have 64MB of L3 cache. It has 8x8MB of L3 cache.

* If CCX#0 has a cacheline in the E "Exclusive Owner" state, then CCX1 through CCX7 all invalidate their L3 cache. There can only be one owner at a time, because the x86 architecture demands a cohesive memory.

* All 8-caches can hold a copy of the data. In the case of code: this means your code is replicated 8x and uses 8x more space than you think it does. Code is mostly read-only. With that being said, it is shared extremely efficiently, as all 8x L3 caches can work independently. (1MB of shared code on all 8x CCXes will use up 8x1MB of L3).

* Finally: if CCX#0 has data in its L3 cache, then CCX#6 has to do the following to read it. #1: CCX#6 talks to the RAM controller, which notices that CCX#0 is the owner. The RAM controller then has to tell CCX#0 to share its more recent data (because CCX#0 may have modified the data) to CCX#6. This means that L3-to-L3 communication has higher latency than L3-to-RAM communication!

-------------

In the case of a multithreaded database, this means that a single multithreaded database will not scale very well beyond a CCX (12-threads in this case). L3-to-L3 communications over infinity fabric is way slower, because of the cache coherence protocols that multithreaded programmers rely upon to keep the data consistent.

But if you run 8x different benchmarks on the 8x different CCXes... each of which were 12-thread each, it would scale very well.

-------------

Overall, the problem seems to scale linearly-or-better up to 16ish threads. (8x is 6762.35, 16x is 13063.39).

Scaling beyond 6-threads is technically off a CCX (3-cores per CCX on the 7401), but remains on the same die. There's internal infinity fabric noise, but otherwise the two L3 caches inside a singular die seem to communicate effectively. Possibly, the L3->memory controller->L3 message is very short and quick, as its all internal.

The next critical number for the 7401 is 12-threads, which is off of a die (3+3 cores per die). This forces "external" infinity fabric messages to start going back and forth.

Going from 12-threads (10012.18) to 24-threads (16886.24) is all the proof I need. You just crossed the die barrier, and can visibly see the slowdown in scaling.

--------------

With that being said, the system looks like it scales (sub-linearly, but its still technically better) all the way up to 48 threads. Going beyond that, Linux probably struggles and begins to shift the threads around the CCXes. I dunno how Linux's scheduler works, but there are 2x CCXes per NUMA node. So even if Linux kept the threads on the same NUMA node, they'd have to have this L3 communication across infinity fabric if Linux inappropriately shifted threads between say... Thread#0 and Thread#20 on NUMA #0.

That kind of shift would rely upon a big L3-to-L3 bulk data transfer across the two different CCXes (although, on the same die). I'd guess that something like this is going on, but its completely speculation at this point.
High COL east-coast city
Nim does that. But I myself don't want Python-style syntax. I like braces and dislike semantic indentation -- part of it is that I like showmatch, and part of my aesthetic sense.
For identifiers this long, I recommend using camelCase.
Right, and the much vaunted test suite is proprietary, so the typical end user can't reproduce this test of "every single instruction."

Not that I'm taking sides here. I'm really interested in both the extensive testing that the SQLite team does, and the analysis that John blogs about.
What are you defining as stable? Never changing? That's not something that should even hinted at.

The fact that you can login to a VM and update a package does not make the system stable either (and of course you can actually do this with running containers as well).
Add to that you still need to restart running applications to take advantage of the package update (assuming the packages is a shared lib).

Meanwhile you can push new base images, automatically trigger rebuilds and roll out the update when ready.
SEC Probes Why Facebook Didn’t Warn Sooner on Privacy Lapse
I'll skip it thanks. Notepad, and EDIT.COM, work well for what they're meant to do - be basic text editors on the Windows/MS-DOS platform.
I'm not angry. It's really easy to make a comment and run alongside one perspective of many thought paths. I'm entertaining my own here, just as you are doing. It's varied and diverse. Just because you don't understand my perspective doesn't mean it lacks value.
Not sure how back you've gone in terms of that tech, but you may enjoy the Connections series (several seasons, although the earliest were the best IMHO).

It starts with some modern concept (modern being a couple decades ago when it was made), and traces the random circumstances that led to all the various inventions that got us there.

A favorite game of mine to play would be to try and put myself in the shoes of people from that time based on the conceptual understanding they may have had of things back then, and try to imagine the magnitude of the breakthrough something as simple as a pulley or gear may have had, and what sorts of problems I might try to solve when THAT was the cutting edge tech.
My first job (in high-school) was doing QA and eventually coding for a 4 person software first. I don't know how common this actually is, but I don't see why internships/apprenticeships can't be a more common thing for even teenagers (instead of just those in university).
It's the same behaviour of ordinary users, in general. A developer who uses your library is, basically, a user. They see your work as an obligation, not as a gift you are giving to everyone.
It's not public, but that's why it's a trade off.

Yeah, I won't be broadcasting it publicly, but it would be stupid to spend hundreds of hours properly securing it and wasting countless hours making anyone that wants to access it jump through tons of hoops.

If there is something that starts processing data or is customer facing, then more work goes into securing and engineering it. If an outage would cause significant issues, more work goes into security and engineering. If it processes personal data, then even more work goes into security and engineering.

I'm honestly surprised this is something that most people don't agree with... Do you really advocate using the highest security and redundancy practices for even the smallest of front end projects?

I'm not advocating throwing all common sense out the window and just eval-ing anything and everything, just that a "move fast and break things" ethos has it's place, and can massively increase productivity in places where it's useful, and a "slow and safe" ethos can always be used when needed. Or anything inbetween.
>Writing native UI code is no more low level than using electron.

For one JavaScript doesn't have shared memory threads like lower level desktop languages do, it's all neatly hidden in JS event loop or your forced to go IPC route. Shared memory multithreading introduces low level complexity but brings performance benefits if you can leverage it.

Plenty of other low level APIs and technologies that you either can't use or are wrapped in higher level sandbox constructs for JS for portability, security, ease of use, whatever.

Writing native UI code often forces you to deal with low level platform specifics but you get the benefits, HTML UI is just a cheap way to do it (not meant in a derogatory way - it's easy to find devs/designers and target multiple platforms from same code base)
Thanks for adding those commands.
I have no comment on crypto but if you're "addictively" using leverage to trade options, I hope you're only playing with your throwaway money. You are practically bound to lose money to institutional investors when playing with options.