skysight-inc/HackerNews huggingface dataset:
You could make a drone that will follow your friends/enemies around and spray them with a super soaker. Use your imagination, the first person to figure out a good answer to your question will probably make a lot of money.
As a Canadian I got my TN at the port of entry. I've talked to Mexican nationals who said they had to go to a consular and pass an interview before getting their TN.

Unless this has changed recently, this comment is not true.
I've switched jobs every year and almost tripled my pay in 5 years. It's stupid to not job hop, I'm making more than twice what my friends do that have stayed put.

In my experience, companies with a ton of job hoppers have better engineers too. The people that hop a lot tend to be more outgoing and amenable to taking risks.

Job hopping is only lucrative because companies take advantage of inexperienced devs and never give raises.
I'm pretty sure end users care about performance and bugs, although certainly you have to get over a significant threshold before it becomes a big deal.
I don’t understand how this “prevents code injection” in any meaningful way. The blog post boasts on and on about how it’s going to solve the problem - but at the end of the day, a code injection bug is still a code injection bug. Sure, the attacker now has to program in a demented, randomized dialect of PHP, but given enough patience they’re bound to get something usable running.

Plus this breaks practically any code that actually relies on dynamic PHP features to generate code, because now the code generators have to be manually edited to spit out obfuscated code instead of normal PHP.
Domainfactory admits security breach after days of silence
Fighting new development is the cause of high housing costs in the first place, and they can stop doing that. The only possible way to solve a shortage is to add more of the things that there is a shortage of.
The Fed stopped publishing the amount of M3 money a long time back. Do your homework. They literally printed 4 trillion dollars to buy up everyone's debt following 2008.
Your argument is that because other people can do it, that makes it OK for Amazon to do it.

If you ever have children, wait for them to make this same argument. It should happen around the age of five.
Well, yes. But they do that by replicating a lot of functionality that might as well be pushed down a level. Because every program with output that people or other systems rely on needs that level of reliability and yet only very few provide it to a degree that the company behind it would accept liability if it doesn't.

Usually 'working' and 'reliable' get redefined to 'working with what we've tested it with' and 'reliable insofar as our statistics indicate'. Without knowing for sure that you've really covered all your edge cases you're a typo away from some disaster. Fortunately most software isn't that important. But for software that is that important these strategies, even if imposed from the outside rather than embedded in the language will pay off.
Sure. All they have to do is tell themselves that this data is totally being used for a good purpose and Europe is just being over regulatory.
Its also very similar to many opinionated Python style guides (minus the !, and where @ is used for decorators [which are a bit meta like macros])
And, very importantly: input validation at the edges. Way too many systems assume that the data they are fed is consistent.
The new keyboard is great. I expect they’ll figure out the defect issue, but the design is a classic example of Apple changing tastes (as seen in keyboard and trackpad preferences in higher end PCs now.) Their TV push will be analogous and it doesn’t make sense to read so much into the existence of a repair program.

I would agree that producing TV isn’t a Steve Jobs “bicycle” move, though, and that’s the same with the non-swappable-parts strategy they employ in hardware, even though the software is liberating and creative. I think they are pursuing the right strategy, but wouldn’t it be great if Apple’s content push could come more directly from users’ copies of Final Cut Pro?

(I’m a power user and Marco Arment doesn’t speak for me.)
This may be an unpopular opinion, but I’m not a big fan of containers and K8S.

If your app needs a container to run properly, it’s already a mess.

While what K8s has done for containers is freaking impressive, to me it does not make a lot of sense unless you run your own bare metal servers. Even then, the complexity it adds may not be worth it. Did I mention that the tech is not mature enough to just run on autopilot and now instead of worrying about the “devops” for your app/service you are playing catch-up with upgrading your K8s cluster?

If you’re in the cloud, VMs + autoscalling or fully managed services (eg S3, lambda, etc) make more sense and allow you to focus on your app. Yes there is lock-in. Yes, if not properly arhitected it can be a mess.

I wish we would live in a world where people pick simple over complex and think long term vs chasing the latest hotness.
React has been around for five years now. JS ecosystem change fatigue articles and comments are what's really going out of style. ;-)
Anybody familiar with this method? It looks very intriguing as it looks to be combinging Bayesian posteriors with the neural activation function. Haven’t had time to dig into myself, and it would be nice to know an outside perspective on it.
"Insider trading" is very different from "planned sales as part of normal executive compensation", despite what your chosen financial software may say.
Shadowrun was right.

https://cvdazzle.com
>So there's 49 other states __you__ can move to and not deal with Prop 13?
That's reality right now and if you're going to be headstrong that's how the community will respond to your reasoning.

Ah yes, and there's the classic "I got mine, so screw you" mentality of California. What a nightmare.
I am in the e-waste industry. There are thousands of companies doing this already. This article is written like the BBC just discovered this. While there are many small processors there are also big ones like Arrow Electronics. The hottest item is phones. There is a small shop down the road from me that processes 300K phones a month. They are not capital intensive but are very labor intensive. Most of the money is in reuse. They clean and test the phones, grade them, and sell them on. The non-working ones can have their parts salvaged. The true scrap is sent on to smelters to extract the valuable stuff and dispose of the rest responsibly. Most follow the Responsible Recycling (R2) standard. Some things like cathode ray tube glass has a negative value, meaning you have to pay someone to dispose of it.
"Technically it is too late for beta, too early for R3, but send a PR with your changes nevertheless..."

https://github.com/ansuz/RIIR/issues/35
https://transitiontech.ca/random/RIIR
From that argument, we should be coding everything in hand tuned assembly, because hand tuned assembly gives a 10% to 200% speedup over C.

The number one slowdown I've seen in rendering web pages, were not bad algorithms or bad programming languages, but bad database queries.

And if that's the case, there is a lot more optimization in the DB to be gained than rewriting your back-end to C, say.
I mourn whenever a consumer technology becomes streamlined, homogenized, and commoditized.

There's a pattern - it happened with smartphones too - where a new technology appears, and at the beginning people engage with it directly. They use it, they do things with it. And in that type of relationship there's the opportunity to have fun with it. But then as the new medium grows - as it becomes more economically lucrative and scales to an exponentially bigger audience - it's made to be more efficient instead. Eventually users no longer use, they consume.

Think about how weird and wonderful the first iPhone apps were, with their kitschy skeuomorphism and novel uses of sensors. The accelerometer-based lightsaber. The sound boards. The odd and interesting domain-specific utility apps. Even Instagram had personality back in 2010. And then people would jailbreak their iPhones, so they could add widgets and toolbars and ridiculous neon color themes. The smartphone started out as a magical anything-object that people looked at as its own entity, just as web pages started out as magical worldwide bulletin-boards that people would put together and decorate for their own sake.

These days the smartphone is boring. It intentionally falls to the background, serving as little more than a stylish content-pipe feeding your every craving. It is minimalist and inoffensive and ever-present. Even apps are supposedly on their way out. The very action of opening an app and doing something is seen as a piece of friction, keeping people from consuming content as effortlessly. Google Assistant and Siri would rather predict what you want and serve it to you before you even ask for it.

Play is how the human brain stays alive, and it can't happen without back-and-forth interaction and tactility, and user agency.
Now convert that into a blog and post it to HN. The fight vs. bloatelitists has just begun!
I have also learned eiffel and read Meyer's book. The terrible standard library with the deep inheritence trees was my main complaint about this language. All his critics about C++ were very insightful. At that time almost nobody was speaking about immutability (GRAAL was called a language without variable). Java was almost revolutionary with its immutable strings.
The selection of this metric is not some recent political decision - the headline number has been U3 for a loooong time, and its definition was decided by the UN-affiliated International Labor Organization.

It's not a good measure, but it's not a case of politicians picking a convenient metric, it's just a case of a bad metric being optimized for.
Are people surprised that real-time image analysis has been commodified or that local governments are already applying this technology ahead of policy discussions?

Clarifying edit: I'm not being disingenuous. I may be too close to the technology to grok why this thread is a down-vote minefield. Running OpenCV on an Arduino board is years-old proof-of-concept stuff and now I have an AWS DeepLens sitting on my desk that can name which of my neighbors walked their dog past my house.
I’m actually working on this. See ‘users controlling moderation’ section here: http://blog.getaether.net/post/175104485127/aether-news-upda...
> you can rely on and document experience gained through companies that are now out of business through letters from former supervisors or colleagues.

This is exactly what I was looking for, thank you so much for your time. I'll contact your firm if it turns out that I need more assistance.

Again, thank you.
>Conduit will become Linkerd 2

I have not been following this space, is anybody willing to provide background?

It looks like linkerd developers re-wrote their Scala service in Rust, citing smaller footprint and lower p99 latency as wins from this approach. As a JVM-hater myself, I fully believe this conclusion, but my mind is open to change. Certainly there's at least some nuance? Furthermore, to my knowledge the Netflix plumbing model puts the middleware as java libraries rather than java services, avoiding going through another JVM like Linkerd does. Are stacks like Java and Ruby sufficiently poorly suited for middleware services that developers should be rewriting-in-rust away from them?
"proper package" in that it has a toml file and a uuid, but it can't be controlled by the package manager in terms of updating, handling installation, or pinning versions. The stdlib "packages" are an awkward in-between state that isn't usable the way a full package would be, the only thing it has forced people to do relative to being included in Base is now you need to do `using LinearAlgebra` to load it in downstream code. That might get fixed eventually so you can express that you depend on the LinearAlgebra 1.0 API to isolate yourself from stdlib breakage, but there's no way to do that today short of doing the work yourself to create a full versioned package with the same content.
شركة نقل عفش من السعودية الى الاردن
This paper, perchance? [0]

[0] https://www.researchgate.net/publication/282328265_Fiction_a...
> And a perfect solution according to markets is the solution that does the job for the lowest cost over time.

Yep. If we actually valued correctness, the market would place some cost on incorrectness. Security is a common example of this. If we wanted, we could punish software developers or publishers for shipping security bugs (for example, making them liable), and then we would see an immediate shift in how software was written.

That's not necessarily an endorsement of that position (it lacks enough nuance to even be remotely considered a good idea), it's just a fairly illustrative example.
How to Build a DApp Game App Like CryptoKitties?
How could software prevent rewriting history though? It can't be physical impossibility. If ensuring client rejection is a solution to this, then won't a git client also reject history changes?
it's extremely political. By the way you define it you can explain the need for some reforms or display how good you were.
As long as I or you can use it to track the coming and going of your Congressman and Senators, at the same price that Amazon charges others, I guess it is okay. That nice townhouse he visited with the attractive blonde who lives there, while his wife was out of town? It's ok for me to track and then publish the info, right?

We're all equal when we are in public view, right?
You're acting as if React makes it impossible to do anything else. As needs to be iterated every time we have one of these threads: you're still free to do it the "old way" -- writing your backend in X lang, your iPhone app in Swift, your Desktop apps in C++, your Android app in Java, and your web frontend in HTML/SASS/JS/jQuery. Nobody is stopping you.

The truth is that people want their apps on multiple devices these days, and many apps wouldn't exist without react, at least not a port for your platform of choice. Yes, React sacrifices convenience for performance, but that has always been a trade-off. You'll notice very few people writing apps in C these days.

That being said:

What native features are you lacking?

What apps are you using that are noticeably slower than native alternatives?

My main complaint with React Native is the memory usage, but that is getting better and better and my computer has tons of RAM these days.
Job reqs are a lie, and a lot of jobs (I almost want to say most, but I don't have data to back it up) never even make it as far as the job boards. The ones that do are often not even drafted by the hiring manager, and just written by someone who asked "So, what kind of skills would be nice?". Most companies will absolutely hire outside of what's written. They don't have much choice unless they're looking for entry level folks. Competent senior folks get snatched up very, very quickly, so if you're looking for something too specific, the req will stay open forever.

At least, that's been my experience working in both Canada and in the US, and I've never been close to Silicon Valley (or the west coast for that matter, so if its true there, I stand corrected).
Of course it did. The Fed bought up all the debt it could. This had two effects:

1) It caused investors to search for yield anywhere they could (subprime is a good place to start!)

2) For many types of debt investors knew they could always pass it on up to the Fed!
exfiltrate data to foreign countries (where they may be subject to foreign intercept)

If you're, say, a Ugandan dissident would you rather be spied on by the NSA or the Ugandan government? Tunneling all data out of the country may be safer for the majority of people, but maybe I'm falling for the trope of downtrodden poor who are being exploited by their (presumably) oppressive government.
And then, five years after you've left the company and some system inevitably collapses with nobody having a clue as to what went wrong you'd finally realize the wisdom of all that.

But it's no longer your problem.

So, please don't take it personal, but 'the well intentioned types who write these articles' tend to be the people that then get called in to clean up the mess.

And then - belatedly - the job gets done properly to keep the company in business, assuming there is still time enough to do so.

Just this week I had a nice inside look at the kind of mess gets left behind when the original duct-tape-and-spit guy leaves the company and lets his former co-workers clean up their mess. It isn't pretty, and a chapter 11 isn't an unlikely scenario, so forgive me if I take a harsher than usual look at the attitude that causes this sort of thing.

Note that the 'free market' doesn't have a horizon much longer than the next quarterly shareholder report, and that your typical software product lives a multiple of that interval. So software made with short term goals in mind will create long term headaches.

Your two week marketing campaign gets a pass. But your decade long backend project does not, nor does your real time medical device controller, ECU, database system or operating system.
My bad, I thought it was a PR but it's just an issue with 2 people actually had started work on it: https://github.com/trailofbits/mcsema/issues/220

I understand it's a difficult issue but even with a basic CFG recovery, wouldn't it still be useful to lift code?
That's where we're at in terms of the technology right now. Leafy greens harvest fast vs other plants. And are hydroponic friendly vs other plants.
Some are more transparent then others, in fact some are outright opaque.
With the CLOUD act, this decision makes sense to me. Could you elaborate where the paranoia lies?
Repealing Prop 13 also removes another impediment to increasing housing stock. People who already own property and don't feel the effects of quickly increasing property prices will vote against new development more often than people who have to pay higher taxes when property values go up.
One with a database?
In my opinion, this is mental gymnastics to try to eliminate git from some discussion. There's nothing of merit here. Plenty of people use Git every day to control their software revisions and it works just fine.
Is there a way not to go to secondary when we have an advance parole? Thanks
You can easily prevent this on the server side. The protected branch feature of Github prevents history rewriting for example.
and France, both have similar internet limitations.

https://freedomhouse.org/report/freedom-net/2017/france

https://freedomhouse.org/report/freedom-net/2017/philippines
New information is always being obtained, and abstract frameworks are not always logically consistent.
I feel like there isn't much of an argument made here. It's just "we chose VCS and we're clearly right" with the veneer of examples.

> Git is clearly not a VCS, and it has never tried to be one, and
people calling it one doesn't change that. The absense of a progressing version number and lack of a definitive
timeline, not to mention all the many "unnatural acts" you can do
to a git repo are sufficient arguments to settle this point.

OK - all of these things you can get by having a central authority thereby creating a VCS (by your definition) out of git. So git matches your definition of a VCS under constraints you already have.

>
But in many cases Git is an adequate substitute for a VCS, you just
have to augment it with an out-of-band definition of which tree is
the 'definitive', and settle who gets to define what 'a version'
means. This is why github exists in the first place.

Oh great so you agree that you can make git into a VCS based on your definition. So what's wrong with git again?

>In FreeBSD we have insisted on "proper version control" from
day one, 23 years ago, and while it is a decision we should
revisit periodically, everytime it has come up, it has been
overwhelmingly confirmed as "the way we do things here".

Ah, it's just not "the way we do things here". That's what's wrong with git. Got it.

An argument that might make some sense to me is "the beneficial collaboration features we'd get out of git isn't worth the switching costs". But I just found this written so matter o-factly ("It's impossible to refute this line of reasoning in my opinion.") for something that seems to make no actual point at all
As someone who runs a fairly popular "personal" (not corporate, opinion-based) blog, it is an ongoing fear. We have to try to make sure the things we say are as least controversial as possible. But in a way, this is a good thing.

My blog is about my city, and there are plenty of things we "can" talk about but probably should't. For example, I don't think the business that's in one of the cornerstone buildings downtown is the right business for the neighborhood. But I'd never say it. It'd be needlessly confrontational, my opinion isn't going to get that business to move, they're paying their rent so they have every right to stay there, and all it would do is piss people off who disagree with me.

On the other hand, we generate minor controversies all the time. People who live outside of the city always want more parking, we're pretty strongly against setting minimum numbers of parking spaces when putting in new buildings. We support new higher-density living in the city, many neighbors are strongly opposed to it. As such, we're the target of smear campaigns and any relevant social media post is often swamped with the people who disagree with us. We've also been factually wrong in the past, and some people do their best to remind us of it as often as possible.

The trick is to ignore it. Haters gonna hate. Don't be unnecessarily confrontational, and just roll on without acknowledging your public critics. They're just trying to piggyback off your success.

It's not really a "one wrong word" situation, it's "one word you really knew you shouldn't have said, but against all better judgement you did anyway" followed by "engaging your critics in arguments", then topped off with "caving and admitting defeat because you knew you were wrong all along".

I can't think of a single collapse of a public figure because of one wrong word that wasn't extremely egregious and then handled extremely poorly.
What are people’s thoughts on Loeve? Too old, too much to bite off?
Generate color palette for your website
I'm seeing lots of "help wanted" signs. In fast food places. This isn't progress.
How to drop a green card application and be able to visit the US afterwards? (I’m French, an ESTA country).
That's not entirely true. He's openly opposed to Amazon and to companies that outsource to factories abroad.
It gets downvoted because that topic has long transcended being a discussion about interpretation of available data, and has instead turned into a cultural and moral battle over "liberators of the oppressed" vs "evil misogynists" or "whiny snowflakes" vs "those who pull themselves by their bootstraps".

Almost impossible to make any progress in it without appeal to emotion and in-group/out-group dynamics.
"nothing is stopping governments from taxing physical, tangible things."

When information is the product of the new economy, and where value is created, it has to be part of the tax base.

"Nothing is stopping governments from taxing the gross revenue (such as the WA state business and occupation tax) of ISPs and telecoms in general."

True, but this layer of the value chain is not where the new information economy is being developed.

"Where this breaks is when they start deciding to tax specific types of internet content at TCP/IP layer 3"

'Content' and 'Layer' are separate issues - they are intertwined for pragmatic reasons, and I agree doing it at 'an internet layer' is dumb ... but there's no clear way around it.
Choosing where to advertise by human hand seems like a great way to maximize the effect of a given budget.
Plain old good Java, C#, C++, JavaScript and SQL.

Since 1993, C only when not allowed to use C++ instead.