skysight-inc/HackerNews huggingface dataset:
you will pay. they will get $2. everyone else won’t pay. it wasn’t even worth setting up payment for you. oh and you actually wouldn’t have paid either
Tilt your phone.
I've noticed that the longer your career is, the harder it is to find someone who can replace you. E.g. if a company wants you because you grew MS Office for 5 years and then did the same for Google Sheets, and they want you to help them do the same, there are few substitutes.
Playing online through exchanging letters is slow (e.g. a week per game year), but it definitely has very serious deception and diplomacy.
I think this can vary greatly from company to company, team to team, and individual to individual. I've had scenarios where it's 90% synchronous and others where it was 90% asynchronous.

Edit: this excludes scrum meetings. On the team I consider 90% asynchronous, the scrums we had were more about ceremony than communication.
I'm thinking in terms of a proof of concept with hopeful expansion in the future.
React is a great example of YAGNI and premature optimization. I'm sure Facebook benefits from it, but most websites don't need it. JSX is an abstraction encouraging deeply nested components, which makes state handling hard, necessitating the invention of React Hooks. "Controlling complexity is the essence of computer programming" -- Brian Kernighan. I see a celebration of complexity in modern website development and it makes me sad (I'm retired, I don't get that sad about it.)
>Or it could be like the flu, and mutate / continue indefinitely.

I gather that is unlikely, coronaviruses don't mutate like the flu.

In fact, according to experts, it is most likely that this coronavirus will decrease in severity over time and become endemic like the other several coronaviruses that are responsible for 15% of common colds. Or, alternatively, occasionally returning like a bad flu year. https://www.statnews.com/2020/02/04/two-scenarios-if-new-cor...

I remember reading in other places this may have happened before, something about a really bad flu year in the 1870's that may have been another coronavirus introducing itself to humanity.
And most backend engineers don't go architecture astronaut Kafka, Cassandra, Kubernetes, et al into seemingly straightforward concepts?

The number of times I've seen Kubernetes as part of an on-prem install of enterprise software when there will only be one node was hilarious. That front-end devs get flak seems to largely be because their choices are visible, not because they are any different from the weird heaps people throw together behind them.
I would bet that the majority of Americans do not even have 401k plans or pension plans, and those that do have very little money allocated in them.
I think a person genuinely trying to give advice doesn't act the way Damore did.

But let's say you're right, that his very best effort to collaborate with his colleagues was a divisive attack on their politics. That his very best effort to collaborate involved sticking to his guns to the point it was causing a major internal problem, and then a notable external one. In which case, he's so uniquely bad at collaboration that I don't think they could do anything other than fire him.

But personally, I don't think Damore was almost uniquely incompetent.
I posted 2 months ago about fdir being a glob alternative. However, at that time it didn't have glob support.

I am back again with fdir 3.0. It has been completely overhauled, improving the speed by upto 40% over previous versions, includes a Builder pattern API and of course true "glob" support using picomatch.

Please feel free to try it out! I am here if you have any questions.

P.S. I had to use the npmjs link here because HN wouldn't let me repost. So sorry for the inconvenience.
$20k to $200k
Thanks Bob. Very helpful comment.
If people live a fulfilling life and are taking care by the state when they hit a bad time or go through health problems, they are less likely to want to overthrow the state. This social net requires taxes. It’s a social net, not a racket.
That's probably a swift issue rather than LLVM. LLDB works great for me on C code.
And even if you are able to pay and choose to do so, do you think this means they stop collecting your data? I very much doubt it.
Is this purely careless programming, or genuinely diabolical to use in conjunction with something else to allow for more "interesting" things later?

Never attribute to malice...stupidity. However, I'm guessing since it is Huawei, it will always (deservedly?) be suspect as malice first?
I've been happy to see ATT&CK, yet in practice avoided as a lot of compliance effort for limited value when that same effort can go elsewhere.

The good:

-- Auditing & tuning defense in depth: From a testing/verification perspective, defense in depth should follow both your organizational structure (endpoint, network, cloud, virtualization layers, etc.) and, to economically optimize, double down around attack structure. ATT&CK compliance gives a goahead for auditing your system + vendors for holes in the latter.

-- N+1 standard: Most Elastic/Splunk/etc. SIEM implementations I've seen are half-implemented dirty data messes. The world failed to agree on past efforts like CIM, CEF, CVE, STIX, etc. ATT&CK compliance is auditing your data lake for better SIEM standardization, and an N+1 effort to get folks to agree. If ATT&CK gets you signoff for cleaning your lake, great!

-- Training: A surprisingly large portion of defenders are junior or overly specialized (endpoint vs network vs cloud vs malware vs...)

The bad:

- Expensive. It doesn't solve much more than the above. I'm much more inclined to spend the $ and effort on better data processing & automation & intelligence capabilities instead. Likewise, for auditing, spend time/money on manual + automated red team, or ATT&CK? For big banks & gov, it's more ok b/c the answer is "giant budget; do both."

- Dead end / stepping stone . For the ontological aspect, manual killchain taxonomization is good, but for mapping to real-world data, my sense was, and has only increased, that a lot of that effort needs to be shifted towards (a) centralized logging efforts like Azure Sentinel / Google Chronicle's cloud SIEM's do it for you rather than admin running Splunk/ELK (b) combining w/ ML techniques (BERT?) instead of both the parsing and categorization being 100% manual.

I may be especially attuned to the problem b/c teams come to Graphistry when they realize their SIEM is a mess and can't quickly see stuff like killchains, so are striving for next-level thinking. So we get to see a lot of the many ways manual / rule-based n+1 standards here go wrong. At the same time, I'm optimistic b/c of the automation+ML world we're increasingly in. (Semantic web vs. Google search.)

More on the positive side, we've been working on some anti-misinformation work in covid ProjectDomino.org, and an ATT&CK-like mapping of misinformation has been helpful. Defense in that world is a lot earlier in the understanding needed for automatic detection & response, so manual taxonimization is a good early step.
Yes. To highlight the response to a) - flattening the curve means that the peak is lower, but also that the area is smaller. The herd immunity level is always reached and overshot, but with a flatter curve the overshoot is smaller, and it can also be reached with vaccination. Thus, saving lives, even without full containment.
Trees to Reduce Air Pollution
I agree with the sentiment of what you're saying, but I don't agree with the premise that there are no use cases for single page apps. You can achieve a decent UX for some applications by using small amounts of vanilla JS, but it's simply not possible to avoid re-rendering the entire page without using XHR requests at some point. That is how the browser is designed, fundamentally. Because it wasn't designed as an application platform, it was designed as a document platform.

But some products are actually better as applications, not interconnected documents. For those applications, the browser fights you every step of the way, because that's not what it's designed for. You simply can't compare the UX of document-based web applications to native clients.

An SPA is just the web approximation of a native client. Your application truly runs in the client process continuously, so rendering transitions happen smoothly instead of blank pages and jumping transitions. Everyone would benefit from understanding more and using that to simplify all areas of the tech stack, but the experience that an SPA offers is simply not possible otherwise.
Making my first mobile game
Well, when I am considered a developer AND a stakeholder I may be able to address that AND not be told that I'm going to implement the carousel because "market research" anyways.
This. It is good to have records of your communication. I believe this saved my job at one point.
These type of security vulnerabilities are due to the core OS/APIs being developed by a surveillance company that isn't concerned with user privacy, and they're countless.

There isn't enough will in the Free world to mitigate even the most glaring ones either, such as LineageOS not incorporating the MicroG patches. The end result being more forks, more confusion, and groups of users remaining unprotected.

Commoditize your complements, indeed.
Thankfully pretty much everybody still has the ability to buy into a safe neighborhood with a good school district in the Bay Area.
Exactly - I come from a long line of addicts, some recovered and some dead. I am (now in my thirties, less so when I was younger) always extremely careful when I notice an unhealthy behavior taking a hold of me.

I’m making an exception for video games during this time because honestly it’s pretty low on the unhealthy scale in my current usage, especially with the accountability of a spouse who knows I can be this way and will call me out if it gets bad.
Historically, the optimistic people do better in the market than the doomsayers.

Besides, it doesn't make much sense to claim that it's unfair people are making money in the market, while saying it's too risky to invest in it.
I'm curious, what kinds of pitfalls can occur?
Sneer all you want, Microsoft Basic was a reasonable achievement considering that:

1) it ran in under 4K bytes of memory on an Altair 8800. That means less than 4,096 bytes of memory. Not 4,096 Kilobytes or Megabytes. 4,096 bytes.

2) An enhanced version ran in under 8K bytes of memory. Less than 8,192 bytes. Let me repeat: less than 8,192 bytes.

When you're fitting an entire BASIC interpreter in 8,192 bytes, you're not spending a lot of effort to memoize a search result.

Bill had a lot on his plate at the time. The software started out on the Altair, but all sorts of manufacturers were soon beating the door down begging for versions for the Commodore PET, the Atari, and countless other computers.

https://en.wikipedia.org/wiki/Microsoft_BASIC
Maybe some y'all will hate on me for it (or would, if I got into specifics) but I can find common ground with just about anyone. Although I am very opinionated, I do my best to keep in mind that they're just opinions, and that I don't have the truth.

I don't explain why others are wrong. I just have conversations. And I'm always willing to change my opinion.
You're the target audience for my comment then!

I'm advising writers that some people reading their content may make this association, so they should avoid the phrase unless that is their deliberate intent.
Given that it works reasonably well for rust and c++, maybe that's more a problem on the Xcode or Swift side?
Only for folks who cannot differentiate between a specific combination of words and another similar combination.

I used to be that guy, but I realized that all of my negative thoughts about my views and politics were bleeding over into areas where there was no connection. This article is clearly not associated with Trump or politics at all, and even if they use the "make x great again" phrase.

The only sinewy, tenuous connection you can even make between them is 3 words, so if a person takes such a negative view of Trump (very relatable) that anything with those 3 words plus another noun offends them so much that they cannot read the article, they really need to reassess their mental stability (much like I did recently thanks to @dang taking the time to discuss some mean comments I made here when my account was being throttled for them).
No, they are running closed betas at the moment
I recommend getting the book, it's cheap and a good read. It also lays out a path for those that want to accumulate wealth themselves.
Please write more about this because I feel the exact same.

Use built in HTML forms. Let the page refresh, what's wrong with going to `/orders/{order_id}` page to get information about the order? It is REST-ful and static. Why do you want things moving around and reacting? People of the internet - imagine if the internet protocols were given to us, but no browser existed. Would we develop this non-sense we have today?

What should have happened is the following:

- Develop web-to-native-UI mapper, call that thing a browser.

- Don't let developers style native elements. A drop down should not be designed by people except for the owners of the OS. Yes, it looks different on different OS but your application should be more than putting lipstick on a pig.

- Accept the fact that your application looks different on different OS'es but embrace the fact that your application works intuitively to the users, you have much less to maintain and focus on the logic of your app.

The web went downhill the day `<input>` tag was allowed to be styled by CSS. We had a web-to-native-UI mapper!

I am forever a believer that democratically designed things generally suck unless there is a BDFL who can make shots. Dictatorship is a necessity of great products and services - Steve Jobs to Guido, democracy is good in politics, not in software development. Feature creep from the public will ruin whatever youre buidling. Designers will ravage through what worked well and replace it with "taste".

/Rant, I am getting old. Humans tried to make the web "pop", but instead it exploded with chaos.
How does this work exactly? asking for a friend..
(like the requests from browser to definitely-not-an-ad-subdomain.dastx.me also include cookies set by *.dastx.me content?)
This is the problem. The ways in which it can fail can vary (sometimes you can't even pull logs from the web interface), and if it fails during a production deploy you may be left at half or no capacity.

When something inextricably effs up, rebuild the environment and more often than not, the problem dissapears.
As it currently stands, 15 out of 24 comments in this thread are about the phrasing in the title. It has demonstrably become a distraction, at least in this post.
There are some lighting differences but in this case the main 'disparity' seems to be that everything is in focus at once, since they are not attempting to simulate a camera photograph.
The future(well now too) is machine learning. Don't have to understand. Just feed pictures of what you want it to look like and out comes materials that look like that.

Many techniques like this highlighted on Two-Minute Papers
And battery on mobile/laptop.
Speaking as a young(ish) dev, I think the issue with SPAs is that it's that its use has been conflated with separation of concerns and agnostic backend dev.

What I mean by that is that the way we learned is that the old/wrong way (php style templates) mix front end and backend development, and data with formatting. It's better to have data available through rest APIs and then consume it from something. Which is mostly true if you plan on being available in a reasonable way from smartphone apps, etc. but of course that means that your website should also be a client capable of working as similarly as possible to a mobile app - there you go, SPAs.

We need to find a way to keep those benefits without the bulk of current SPAs. But SPAs appeared for a reason, and it would be wrong to ignore why it happened. Being able to have front and backend devs working in parallel is a benefit, being able to server your content to several frontends is a benefit, etc.

(And if you're thinking "these people don't need apps anyway", the reality is that clients demand to have them - even if it's only so they can bother users with push notifications or collect data, they do ask for them).
Supreme Court Hears Argument Regarding Constitutionality of TCPA
Rattling off the talking points, Check. Barely scratching the surface and avoiding any critical analysis that could potentially derail the talking points. Check. "Rough guesses" and straw mans abound. Check.

And I'm supposed to take articles like these seriously?
Didn't the UK last year rip into Huawei after reviewing the networking software, finding something like 18 different versions of OpenSSL inside of it with various vulnerabilities. At some point, continuing a trend of stupidity should be considered malice.
I agree. I'll share two quotes, from near the start and near the end of the article:

> Vanilla vines need specific conditions to produce flowers and beans. [...] the challenge was developing a commercially viable way to grow the sometimes tricky and labour-intensive crop.

> The vines in the pilot farm are yet to flower, which is when pollination occurs.

So I think it's a cool idea, but I'd wait until they actually harvest once to prove it works.
All governments are Mafias to some extent. That's what it means to have police. The difference is that we expect the government to leverage its Mafia-like power in a manner that best suits its citizens.
Looks like we're moving to a Watch Dogs 2 era faster each day
Well, money bends science. So no big deal ;)
That's exactly what we wanted him to say. Use heavy tooling only where necessary and nowhere else. React is rarely necessary.
Thanks Mike! We will do our best and more.
it just looks like awful code which isn't really out of the ordinary for a lot of stuff I've seen from Huawei.

Other than that, attributing malice to someone just because it's a Chinese company is probably inappropriate.
I would put money on careless/unskilled programming over diabolical. For diabolical code, you would want something that could withstand a few levels of code review.
agree with you (computerGuru) at large scale any rare or corner case happen multiple time per day :-)

Redis was never designed for strong Synchronous replication of transaction or Strong leader election.

So each time a master crash you have a high chance of some recent acknowledged write being lost.
> 40 years ago housing, healthcare and education were vastly more accessible than they are today

More people go to college now than 40 years ago; the price is high because of the easy credit that makes it more accessible now, not less.

As for healthcare, I guess you had a higher chance of being able to see a doctor back then, but they wouldn't be able to treat your illness as effectively as today so it's a tossup depending on what ails you.

Housing is totally fucked now, I give you that.
The market has done even better in the last 10 years than in the 90's.

Besides, I heard the same lament in the 70s, 80s, 90's, 00's, and 10's.

> I don't doubt that's how they feel about themselves and self report!!!

Always better to guess than pick up the book and read it!
Some do. I pay to remove ads from the wunderground app which IBM claims means they don't sell my data. Not sure if believe them, but at least I don't see ads.

https://i.imgur.com/TlOo07T.png
I think the problem is developers/companies only have so much time/resources, and figure that x people might pay for an app/service, but 100x will use it if it's free (with other monetisation strategy), then why bother coding & interfacing with a payment system (and this starts to get convoluted and require and entire department handling payment and tax issues across different countries and jurisdictions) for just 1% of likely users?

Not saying that's the right approach, but that's probably how the thinking goes. Billing is certainly easier than it used to be (that's what the 30% app store cut is for), but can still get convoluted, and might have the perception of being convoluted.
>It's easier and a lot faster to sync your static site to something like S3 or Google Cloud Storage and serve it from there. Now you don't need to secure and update your Linux box or be responsible for its uptime.

I was pushing to *nix hosts I didn't have to manage in early 2000. Actually, one of them I recently remembered and had paid a small lifetime membership for limited static hosting (<$100) and simple shell access and guess what--the pages I put together 20 years ago and supplemental files I had hosted are still there. Not only that, they still render as intended.

I've done absolutely nothing for 20 years at this specific host and it's working today. Yes, the content is fairly static and very simple (its 20 years old) but it's all there. It's a simple shared system and no it wouldn't scale out to support more than probably 10k simultaneous requests but its served its purpose over the years. No, there's no SLA. I'm not saying services like S3 haven't been able to improve on that older infrastructure but it goes to show what very simple systems are capable of.

I've not spent a second of time in 20 years worrying about security, someone else did for a very nominal fee. This isn't a new concept, now we have better scaling available for sure.
Exactly. It's not associated with Trump - so why not pick a title that doesn't risk people even having to ask that question?

The author of this piece is based in Berlin. I'm certain they weren't thinking about any negative potential connotations that this title could hold - they were just reusing a common phrase.
Although tracking it would help, I see 2 issues (in opposite directions): I think there are times when slower performance is an acceptable cost. And, I think that if you allow tiny slowdowns, over time we'll get back here. There's judgment involved.
The above poster's question was specifically about the US.

GDPR does not cover the US. Europe has more privacy laws than the US does.
Are you debugging optimized builds? I have definitely had variables be unavailable at debug time, due to optimization in C in lldb. I would guess that the same could be true for swift's integration.
C is a strawman though when we're discussing C++. Checking array bounds in C (or I'd argue, pretty much checking anything in C) is just a losing battle. The lack of proper abstraction facilities perpetually fights against you. C++ actually lets you abstract checks away into the definitions so that you don't have to modify every usage site.

Regarding optimizers deleting your checks though: is that something you encounter in practice, or just something you see people ranting about in blog posts? Can you even trigger this behavior if you try? Have you seen it happen more than once in a blue moon? I know on my end it's either never happened to me (likely) or it's been long enough ago that I have no memory of it. Even when I actively go out of my way to make this kind of thing happen, it gives me a hard time. Even the most blatant examples you'd try don't end up getting optimized out like this. Try [1] for example. It's both out of bounds and an uninitialized read, and yet the check is still there. If anything it's incredibly disappointing how bad optimizers are at optimizing out bounds checks!

[1] https://gcc.godbolt.org/z/i-FMV-
> owning meaningful equity in a business likely to generate meaningful returns

That's exactly what the stock market provides an opportunity to do.
Decoding morse code using Pytorch
Got your point and totally agree with you. We are going to mention that it's under development and not ready for production usage till we finish supporting all basic functionalities and have a benchmarks results (also for the current release). Actually, we have things to do more than TST that can improve performance. Thanks for your feedback and we are here to get and understand your feedback :-)