Cartwright2

Now I understood none of that, but it sounds like a hack to work around something they tried to fix, or is an ugly way of gluing "old" libraries into "new" libraries which should be handled by the compiler. This is just one example of many complexities I worry are going to bog down any developers who take on ASP.NET Core. Remember we only have to face one compiler error caused by this issue before having to do a deep dive and learn all the inner details to fix it.

I am also concerned about the quality of the tooling. DNX can't handle long paths so I have to develop out of C: drive. This reminds me of Node's almost incompatibility with Windows and makes me worry that the tools haven't been thoroughly tested. DNX is going to be replaced yet again in the near future with a newer, probably less tested set of tools.

On top of that the tooling doesn't work well in enterprise because they have poor proxy support. I'm also worried about "everything is a collection of hundreds of tiny packages", the NPM dramas have shown us that micropackages lead to insanity. ASP.NET was a place to hide away from those kinds of things. Now it feels like it's "C#, as developed by the node community". I think they've tried to make things simple but haven't seen the forest for the trees. The fact that they're bundling dead tools like Bower into the project templates is also worrying. They should have had the forethought not to include any JS libraries that have a high churn rate.

One final thing bothering me is the number of choices of the target framework. Why have there been so many meaningless names like "dnx451", "netstandard", "netcore10"? I sit down to make a web app, and I have no clue what I actually need to target. In the old days we'd pick a .NET framework version and choose either the compact or complete framework. When did this become rocket science?

This was a good article about the stresses of entering a programming career.

The strained sexism tie-ins were unnecessary because most of the challenges she faced are universal, I remember hearing the same gloating conversations and feeling the same way when I was young.

As for the back massages and tshirts with men's names on them, that is a bit weird and should probably be taken up with their supervisor if it continues. It's most likely to be caused by poorly calibrated social cues than straight up sexism. There's nothing sexist about awkwardly showing interest in someone, it's only a problem if they don't take no for an answer.

Chariot for Men:

The premise is the same as all the other ridesharing services, There’s a driver app and a client app, except that what makes us unique is our safe driving feature that other apps forgot to do. We ensure every driver in our entourage is a male.

It's a crazy world we live in where someone would post such a candid article about their own under-performance. This article is embarrassing to the individual, and more importantly, to the company that fired him. I think people need to think more carefully about what they post online especially when using real names. This is permanent now. Any potential employer who searches this man on the internet will see this and I don't think that's a good thing. While some might not be turned off by this person's honesty, I certainly would not hire him having read this article. If anything it shows a lack of a diplomatic filter, not only a lack of discipline.

> I'd give it a personality and a set of values and a rudimentary understanding of how the world works.

I don't think you have any idea how complicated such a task would be.

Is it possible to create and verify a PayPal account against one of these cards? This would allow users to have pseudonymous PayPal accounts. It always bothers me when I go to make a donation that I have to give my real name.

Before deleting your account you should edit out and overwrite as much information as possible. Things like your name, e-mail, and any other fields should be falsified before deleting. You have no way of knowing if their "delete" mechanism just flips a deleted bit or if it actually erases your data.

The problem, in this case, is that the company might notify your employer that you're making those changes. Not sure what I'd do in this case. It might be worth creating some dummy accounts to see what actions actually trigger notifications.

I was banging my head against this earlier last week. It was such a jarring change to visit GitHub and not be able to navigate. It gives me pause to see how suddenly an easily-navigable site can become almost impenetrable with the removal of a single search bar. What are they thinking? The "Explore" menu is worse than useless, too.

It is an interesting case study in UX - the difference between a great experience and an awful one can come down to a single, well placed search box.

What is GitHub's rationale behind this jarringly awful, blatantly bad decision?

How are people able to develop on chromebook-like devices with 2GB RAM? I'm seeing a lot of such devices in this thread and don't understand it. Once I spin up a couple of database servers, a few Visual Studio solutions for the various products I work on, and a handful of testing tools I'm easily pushing 12GB ram or more.

Are these low-end machines being used as hobbyist or frontend-only web development? I can't think of any other explanation.

To answer the original question: Thinkpad X220. i7. Maxed out RAM. It's no portable workstation but I can push it just as hard without worrying about it overheating or failing.

One man's "saving money" is another man's "robbery".

Set up a scheduled transfer from your checking account to your own savings account if you can't manage your own money. Don't encourage these kind of rip-off merchants.

I disagree with the title - I don't think this is a sad state at all. This looks very healthy to me. Backbone clearly had a purpose some years ago and it is unequivocally deprecated now. To me, this is a javascript library aging gracefully and opening the way to newer, better libraries. By removing itself from the list of relevant libraries to choose from in the current year, backbone has helped to reduce decision fatigue.

I hope other Javascript libraries and framework follow this trend until we find a handful of "winner" libraries in the same way that each language has its own "winner" MVC library.