skysight-inc/HackerNews huggingface dataset:
Also in my late 20s, in the US temporarily and nowhere near six digits (academia, sigh) and I've found it okay. You just have to be selective where you apply. I got an unsecured $1000 from Discover (since been increased) and an unsecured $300 from Capital One. I applied for those cards because they both have a reputation for being more friendly to people with empty credit files, and my credit score is now around 715 (TransUnion).

I mean, it's not great, but you have to start somewhere, and I've only been here 9 months. Was very frustrating to have to start from scratch when I have good credit in my home country, but completely understandable.

The really frustrating thing is how your credit score influences everything - apartment hunting, mobile phone contracts, etc. That's the only reason I'm trying to build my credit at all here. It feels like having a bad credit score puts you at a distinct disadvantage in the US, which is something I've never felt before.
It is scary how most commenters here are missing the point. No, not all programming sucks. Yes, web programming sucks more than other things. No, it doesn't have to be like this. Yes, even web programming was better 10 years ago. No, I don't know how to fix it. Neither do I know exactly where we took the wrong turn.
One of my theories is this: had Sun not sued Microsoft over their extensions in JVM, MS would have kept working on their awesomely fast JVM implementation for Windows. That would make Java fast and not sucky in browsers. It would have kept Java Applets as a viable rich web app development option. Flash would have never risen. Java, being a significantly superior language to ActionScript, would have allowed us to build nice RIAs in an efficient, secure and portable way. Gmail and Google Maps would have been implemented in Java. Isometric Java. Get it? Get it? Back end and front end are written in the same language with strong typing and all that. JavaScript would have been dead by now. World would have been a better place.
It occurs to me that these courses have been teaching what might (should?) be considered a naive view of memory; you show me a traditional cyclic data structure and I'll show you a concurrency bug. I suppose that's fine in 1978 when no one imagined they'd be dealing with multi-core microcontrollers, but today, when you find yourself using a "systems" language for non-toy work and you reach for a tool as sharp as a raw pointer, those naive data structures are frequently (usually?) inadequate.
Without specific examples on what your frustrations are, my best guess is that you are just overwhelmed.

It was not long ago that I was in a similar situation like you, all these overlapping technologies looked unnecessary and redundant. Just the node ecosystem by itself, felt like a pile of crap that depended on a bigger pile of crap. For a simple application like "hello world" in React, I have to choose between a large number of possible combinations of packages and install and configure god knows how many of them.

But once you take sometime to adjust and familiarize yourself, you discover that each one of them is a little jewel and are the quite opposite of crap or hack you initially thought. At least that's the conclusion I arrived to.

So, my advice is to just take your time to familiarize yourself with as many technologies as you can in every aspect of web development. After the initial shock, you will start appreciating things and you will realize that they are made by excellent engineers and each has its own merits.
I could probably give a nice rant for each distro I've tried and why they're all horrible. Ubuntu is probably my favorite, but IMO there is no "good" when it comes to OS's.

Every single UI and every single complete set of defaults has a fair number of things wrong with it. Instability, insecurity, lagging feature set, slow ui, ugly and non-intuitive ui, bad documentation, inconsistency everywhere. There is none that are good.
Yes. And while HTML5 brought a lot of awesome features, it also created another set of problems, the least of which, is the syntax is impossible. There are 100 "right" ways to do things now, when in fact, a language should specify an exact way of doing something.
> a fairly long-lived and large code-base

Such could be spaghetti on any platform. To understand web programming, I wouldn't start with something big and old. I've been doing web programming for more than a decade, and I still don't get the majority of web frameworks. Start instead with the basics, and work your way up:

1. HTML. Don't view the source of websites and web apps to understand HTML. Read a good book or tutorial. HTML Dog is a good one.

2. CSS. Likewise.

3. JavaScript. Definitely don't try to learn JavaScript by viewing source either. Instead, maybe HTML Dog. There's also Douglas Crockford's _JavaScript: The Good Parts_ and David Flanagan's masterpiece, _JavaScript: The Definitive Guide_. I don't know how I would have ever understood JavaScript if I had not taken the months to read Flanagan's book cover to cover.

That takes care of the client side. For the server side, it should come much more easily. Basically you have a database, like I'm sure you're used to. Then you need a web server, like Apache or Nginx, and some kind of glue language like Python or PHP. Many people put a lot of code here. But I like to keep it pretty thin: like the database and the browser just talking to each other. Even so, just running this side of the affair can be a full-time job in itself.

I recommend at some point familiarizing yourself with the HTTP protocol in general: all the headers, request methods, etc. Basically once you can use Telnet to imitate a browser requesting a page, you'll feel more comfortable with how simple it really is.
My take on this is that backend developers have always been at odds with frontend developers in terms of being given larger salaries than frontend while not having to keep up with new UI technologies and simultaneously downplaying the skills of the front end programmers.

So now, when you have to learn about the web platform since you just cannot ignore it anymore, you are feeling pretty overwhelmed, and can't help yourself -- you fall back on what you know, which is to shit on the skills of front-end developers.

I say this as someone who has done front, back, database, ops, on web-based and desktop stacks.
What you're witnessing is the migration of complexity to the frontend. It's becoming very difficult to find a backend problem that doesn't have a well-defined, generally accepted solution and accompanying FOSS that you would be stupid (or even borderline criminally negligent) to ignore. In fact, full-stack programming in general is boring enough that I welcome anything that stirs the pot a bit. That said, having tried at one time or another PM, management, and sales: programming is the worst monetizable career option, except for all the others.
I meant it as a conciliatory opening...

What I meant is that if you care for economic security and lesser inequalities, then you have to fight for the whole liberal agenda (improving the coverage of all risks), not just one issue, otherwise the bad guys win this time, and the next, and the next.

I you think UBI's worth fighting (I don't), your only chance to succeed is in the context of advancing that liberal agenda in its entirety over the long term.

And right now, with Obama's legacy and Trump on the verge of winning, the main social front is social health insurance. Sadly I don't hear many tech people on that issue (for hypothetical reasons laid out in the article) and I reckon the whole UBI discussion has a responsibility in that deafening silence.
US teens often forced to trade sex work for food, study finds
Alas, the weight of history is against reason here.
To be honest, I (personally) am not your target audience. Nothing will get me to spam my contacts. I'm sure the audience exists for this, but it is not me and I don't know them.
How can you know what constitutes "relevant" though? There are loud voices in the community that seem right at first but the more you learn, the more you realise you may have been led astray. I guess that's a way of learning, but that particular path to enlightenment is covered in litter.
I'm more unnerved by how few maintainers so many critical/core open source projects/libraries have, whether in web or otherwise.

However high our project or company's bus factor gets, it's concerning to realise that the framework or critical library underlying has a bus factor close to one. We can certainly adopt it, but that's folding in a lot of new complexity. o_O

This applies irrespective of the language, incidentally - it's often true in Java/Python/Scala even as in JavaScript/npm, as much as people like to bash on the latter.
But how does Alexa determine the most popular sites to begin with? I’ve never asked myself that.
Yes.

Whoa. Betteridge's law doesn't apply here. Weird!
> The article says that Yelp has been ordered by a judge to remove a few posts that have been found libelous. Yelp is refusing.

Yelp was not a party to the case.

> It's also not a case of prior restraint since it happened after a trial and a verdict.

Yelp was ordered to do something, but Yelp did not receive any opportunity for a trial.
Any software, no matter what type, that evolves over time will become a series of hacks on hacks. The more the frequency of evolution is the more hacks will be there. Unfortunately the frequency of evolution in any web app is way way too much then other kinds of applications.
Nook Support – Call Toll Free No. And 1(844)305-0086
Your comment is both ironic and hilarious but I'm not sure you have the perspective to understand why. Thank you for "explaining reality" to me with your "what makes the most sense" argument about why the successful turnaround of Hostess is a "crock" that is ethically dubious and screwing the common man. The bottom line is that in a capitalist society reducing costs is required to stay competitive. The only way to artificially inflate employment is to mandate it with regulations. I was curious what mandates you would have, perhaps banning robots so that all baking had to be done by hand? Or if it's not the raw employment numbers you object to, but rather the pay differential between management and labor, how would you force a multiplier that is fairer to without being gamed? I talk to people who argue views like your's regularly and they collapse when logically analyzed. I am hoping you can explain it to me better.
When you only have two options thats what you get. Such polls are meaningless.
The US has had an interest in Israel long before nuclear weapons were a factor.

Stability is only a concern because of the critical suppliers there. Notice how little interest is paid to places like central Africa where, apart from Nigeria, there's no productive oil fields.
Thanks for that. I caught a 403 in the logs for PriceHipster, logs confirmed that CloudFlare (nginx/cloudflare) blocked it.

If it is yours, thanks for reporting it, I have pushed the fix down the pipeline. Its not giving a 403 anymore, but still doesn't render properly.

I have tried to debug it with a different engine but it looks like the site has JS based browser detection (not based on user agent strings). Since its a headless browser, some JS functionality is unavailable, and super dynamic sites break. Another limitation I am working around.
weird. commenters seem to be either new web devs, or non-web devs at all judging from comments and cries.

web development is as hard as any other development environment. you must know a lot of stuff, hacks ARE NOT mandatory at all and it is not as bad as people tell you.

maybe you just work with terrible base code is the answer?
Or it would have turned into ActiveX. Great on Windows, not so great (if extant) on anything else.

If anything, Flash was multi-platform. You got the same flash on Linux, Mac and Windows.

"Microsoft Java" would be anything but.
Web programming is ok. A lot of the complexity comes because it is actually two different problems:

1) The problem of displaying a (mostly static) page of HTML

2) The problem creating an application

There are web frameworks in existence that solve either of these problems, but things get ugly when people don't think about which problem they are trying to solve.
This post makes me sad. Javascript, CSS and HTML can all be used powerfully, performantly and in a managed way where anyone can come on board and contribute. Facebook, Google and Microsoft all use the web stack to run huge companies. To broadly paint this web stack that so many people poured countless hours into making, as 'impossible' to use is doing it a great disservice.

But hey man, that's just like your opinion.
This has nothing to do with democracy. This is what you get when you have a majority based voting system with centralized power structure. Democracy in its origin was about the separation of powers and the involvment of citizens in governance.
While I hate css, sort of like js and hate html layout, a lot of the problems come from accessibility. In that, it's so accessible anyone can do "web". This means you get non-engineers with no engineering background put into situations where thinking about things from an engineering perspective would really help and might produce actual workable solutions.

Like wtf is this:

https://www.npmjs.com/package/string.prototype.endswith
https://www.npmjs.com/package/ensure-string-endswith

str.slice, str.indexOf are standard lib. Adding another layer of complexity for basic string functions that could easily be done natively is very poor form. This kind of stuff happens all the time in the web world. There's a layer of "lack of competency" bootstrapped on top of what I would consider a non-intuitive base.
HTML5 seems significantly less advanced than Java AWT was in 1997.
I can change color of the boxes. Something animates from left to right. But I can't hear anything. (Android 7, latest Chrome.)
Neither of these are going to happen. Closing the EU subsidiary would be a PR disaster, especially after the recent lawsuit (Max Schrems vs. Facebook).

While the EU obviously wouldn't block access to Facebook, I doubt that the cost of complying with regulation would be larger than shutting down their subsidiary. Think ad revenue, declining user base due to bad PR, and I don't think this move would go over well with their investors.
Thanks, but there are many cool things not widely known from Soviet space program. Like first landing on Mars (Mars-3), Phobos program, Zond program, preparing a Mars launch during Cuban crisis, Buran program, BORs, hypersonic research in 1990-s...
I think the question then becomes: How do I make my code more like VSCode and less like, well, everything else?

I'm not sure the answer is as simple as "use typescript".
As SSD explodes in capacity and HDD struggles to keep up look for "archival grade SSD" to emerge as a serious product.

I know there's a ridiculous amount of offline data that must be maintained and tapes aren't always a practical solution.

Manufacturers are being very conservative when it comes to retention times. I haven't heard of anyone losing data because they left their SSD powered off for two long, but if you have any anecdotes or reports to share, by all means.

Early SSDs were temperamental, flaky, and would burn out quickly. The current generation is durable, almost impossible to burn out, and seems to hold data for years even when powered off. It's like the bad rap that plasma screens got for burning in even when that problem was addressed by the manufacturers.
A general-purpose operating system really seems inappropriate for 2kB of RAM. In that space I think it's all custom applications doing very specific things.
You can't really compare "web development" to "application development". I think it's more fair to compare a single web framework with a single native framework. The web ecosystem of frameworks is much larger, meaning there are far more options, much more to adapt to if changing projects. Switching from a well-written iOS codebase to a well-written Android codebase would be no different then switching to a well-written React codebase.

> I've been doing some web development on a fairly long-lived and large code-base

Perhaps it's just not a well written codebase. It's extremely easy to write bad code for web, where perhaps it's slightly harder to do for native development (although still very easily possible of course). It's also very possible to write good maintainable code for both as well.

> I'm not even talking about the fact that everything has to be stateless

It doesn't have to be stateless. Take a look at React.

> just the fact that it really feels like there's no consistent way to do anything

That's pretty much the same with application development. Perhaps not as much for Android/iOS themselves since there is basically only one option for each of those. Even within those there are many many ways of doing everything. It's up to everyone working on the codebase to keep things sane. That's no different with web development.
> Facebook, Google and Microsoft all use the web stack to run huge companies.

And they throw huge amounts of resources at the web stack to do it. It might work for them, but I'm not sure that makes it powerful, performant, and manageable for those of us who aren't huge companies.
Sure, that's possible, but not necessary. Devs might have been smart enough to stay away from extensions. Microsoft might have been smart enough to not push it too hard. Your example of ActiveX actual supports that -- ActiveX never became super widespread, remaining a niche thing. Also keep in mind that this was only few years before OS X was released bringing the 2nd consumer desktop OS back onto the market.
I have been waiting for the dust to settle on the "Node is the worst idea of mankind" vs "Node is brilliant" before taking a look into it.
oh, one other thought, if you are a TDD advocate and TDD all the time and are quite productive. Try this, code something without tests. A curious thing occurs, your software mostly works fine, it's often correct straight away. Basically, you learnt how to design and code. The tests are just feedback. The code itself should also be surprisingly testable if you wanted to test it (if not, still lessons to learn about design and coding). Now, since you are coding and designing pretty well without tests, pay attention to what actually breaks. Gives you a good idea about what kind of Tests are important. Then think about the minimal test that would have stopped you making the mistake.
I wouldn't specify 'median' exactly. That sounds too technical - it doesn't have the same innocence and emotional appeal. I'd mention what other local companies are hiring for the same position at, and mention being surprised they aren't offering at least that. Or mention having friends that got hired for the same position at a salary that's 10k more than you're being offered. If you do it smoothly, I think the worst case scenario should be that they say they can't go any higher, or that they come back with a higher offer that's only 1/2 or 1/4 more than what you mentioned. Like Sun Tzu said, don't corner the enemy.
HBase secondary index and big data analytics application, 1.0.7 released
What's sad is the zillions of hours wasted by engineers on an inherently flawed stack. What's sad is how ridiculously complicated it is to create and manage relatively simple UIs. What's sad is an entire generations of programmers growing up and thinking this is normal.

Programming is supposed to be about creating platforms for each other so we can continue solving higher (and higher) level problems. This web crap has us stuck fighting in the mud going nowhere.
Oh I wish I'd learned this last year when I had a Dynamic Programming module in Systems' Biology course. The name never particularly made sense to me, and seemed like memoizing was the core principle -- which is definitely smart, but I didn't see a reason how it was dynamic. :)
The last 2 sequence boxes for each type of hit wrap around to a new line (firefox). Pretty cool for 100 lines of HTML and JS.
The difference is in human-enhancing features (ABS, traction control, gearboxes) vs. human-replacing features (collision avoidance, routing, situational awareness).

The best human drivers can get by without the first set of features.
Yes.

I got this realization during a study project where I investigated the use of secure cookies (was 2009, it's public [1]). It's just one example, but you can find similar things everywhere.

Sessions in Web applications are realized using cookies, which is not a very good way, because once someone manages to steal your cookie your session management is broken. And there are plenty of ways to do that, because there is no good separation of the session from the rest of the functionality. Because both cookies and sessions weren't in the design of http/html before, they were a later addon that. So was javascript. So were many other things.

The thing you have to realize though: Things work. It's been the most successful technology of the past decades. There is no point in moaning that things would be much nicer if we'd redesign them from scratch, because it isn't going to happen.

[1] https://blog.hboeck.de/archives/681-Study-research-project-a...
this link was here on HN a while ago, but on Medium: https://medium.freecodecamp.com/how-not-to-bomb-your-offer-n...
Alphabet, Sanofi to Invest $500M in Diabetes Venture
My app uses cookie-based sessions (as does HackerNews), so the authenticated section will not work if you have cookies disabled.

I tested in Chrome Win 10, with cookies disabled and privacy badger on and the capture page works fine. I want to debug the issue further to see whats preventing the locations from being displayed.

Have you tried clicking on the gear icon? That shows a list of locations.
STEM to Steam: How Coffee Is Perking Up Engineering Education
I've done front end work for nearly a decade now. You're right and I think frameworks are a big part of the issue.

Looking at how to do something on the web there is a different way to do it in React, Ember, Angular, jQuery UI, Bootstrap, ExtJS, and about 50 more slightly lesser known frameworks. They don't interoperate well at all. Yes it all boils down to HTML / JavaScript in the end so there is always an integration point but try writing a component that integrates well in even 2-3 of frameworks.

Honestly if more people taught solid coding structures and the DOM API (which, yes it's awkward but with the features HTML 5 brought in plus well structured code it's not that bad) you could have a smaller, handful ways of doing something properly and you could even share components far easier.

Granted frameworks are not the only problem. But, in my opinion, they've severely splintered the way the web is developed.
>Can you recommend any good resources to help me orient my mind to this new way of thinking?

The thing about web frontend development is that it suffered from the browser wars and having to appeal to amateur developers. Amateur developers love "Worse is Better"[1]. Basically sacrifice all consistency in favor of simplicity and getting started quickly. "Worse is Better" makes things simple to the point of making ugly hacks for certain situations that don't fit that extreme focus on simplicity.

The browser wars made everything horribly inconsistent. Microsoft's strategy was to make the most broken non-standard code possible automatically work and everyone had to emulate that.

The most clean frontend development I've worked with was Angular with ScalaJS. Typescript in Angular 2 should be really clean. The underlying web browser stuff will never be cleaned up since it has to be backwards compatible.

[1] https://en.wikipedia.org/wiki/Worse_is_better

Edit: Replaced the JWZ URL with wikipedia. Apparently JWZ has some anti-hacker news redirect code on his site.
I think this is for a different app, could you please move the comment there?