jnevill

tl;dr He eats mostly raw fruits and veggies and gets his liquids from those. He had an "Addiction" to processed foods. Clearly he has issues with food and is compelled to share it with the world. It's about as obnoxious as you can imagine.

It's accurate. This book is being ripped apart by scholars across many different disciplines. It's a lovely piece of trash that makes Wolfe look as bad as this article suggests.

In the same paragraph where "Higher Dimensional Black Holes" is mentioned, the journalist hedges the outlandish suggestion with "But no theory yet captures the whole story. “I do not think that there is any remotely credible hypothesis proposed at this moment in time,” Zaanen said."

So... "Yea.. uh huh... interesting concept, not a chance" to paraphrase.

I'm more interested in finding a solution to the problem then I am about protecting my domain of knowledge, or insuring that my coworkers are aware that my domain is special and mine. I can't help but feel that this article comes from a perspective of competitiveness rather than problem solving. Perhaps the reason so many seem to agree with this (even tentatively) is the competitive culture in so much of IT (at least that I read about). I'm glad we don't have that where I work.

Has that never happened to you? You are stuck on a problem for what feels like forever. It's complex and difficult to keep completely in your mind at once. You've hit it from every facet that you can think off. Then you explain it to someone that knows very little of the problem and they throw out a little perspective, maybe preceded with a "Can you just..." and it may not be the solution, but your mind sort of jump starts down a different path than it had before.

I see this "Can you just..." business similar to the advice that you just stop working on the problem that you can't solve and think about something else for a while. Take a nap, go for a walk, have a drink. Wait until tomorrow. Often times the problem isn't that the problem is difficult to solve or that it's complex (it is), but rather that you are too mired in it to come up with the solution. "Can you just... " suggestions often pull me out of the trees so I can see the forest.

I agree completely. Going a step further, as OP has and shutting down potential helpful new perspectives and solutions by implementing a "jar" is reprehensible. When I've been mired in a complex problem for hours and I'm not any closer to a solution than when I started out, helpful "can you just" perspectives is often the key to unlocking a new line of thought that allows me to come up with the solution. Implementing a jar is like having someone pay you to ignore their often helpful perspectives. It's reprehensible.

I guess another way to put this is... I'm more interested in finding the solution than I am in making sure that everyone around me thinks that my domain is special and complex and that they don't share it with me.

Having dealt with both, I'm split. I think, in the end, I'd rather model the DDLs and have everything point to separate database on the same server or a new namespace in the existing database. You give enough rope for the customer to hang themselves, but sometimes their requirements are to build a gallows.

What happened to France?

Speech can definitely be violence and suggesting otherwise trivializes emotional abuse and trauma faced by those that suffer from PTSD and other mental illnesses.

I don't think it needs to be Facebook to not be fucked, but I agree with OP that it could change it's user metrics to better affect behavior. Maybe similar to rep here on ycombinator.com where you get downvoted by the community if you are an ass or not adding productively to the conversation. Combining rep with privileges like stackoverflow.com where a user can't DM until they hit a certain rep, or can't cause a notification on other's devices when they tweet would curtail sock-puppeting and other trollish behavior that plagues Twitter.

As for up to date news, I follow Google's top 10 searches in Feedly (where I follow hundreds of sites) and it works as a pretty decent up-to-date top news trend that gets updated every hour or so. I can appreciate if every hour or so is too slow for some folks though. I'm not in media, and don't really care if Rihanna fell of the stage a few minutes ago during her concert, but I totally get it if others do.

Same here. I have an account, but I've never found any use for it. I've tried a few times, but it offers nothing that I want.

I tend to be more "Social" on sites that focus on a specific topic like StackOverflow, Blogs that I follow, Facebook for friends and family, so Twitter offers nothing there.

Others seem to use twitter as a new aggregator where stories they care about get bubbled up by their followers. I use feedly though to track the hundreds of sites I care about and I've gotten very adept at filtering through the content I don't care about using it.

When I have used twitter, I've found the amount of content overwhelming and I hate that I feel this need to "Catch up" since last time I looked at it. It's endless monotony.

If you are a developer worth your salt and not even registering on that scale, then I'm going to go with "Underpaid". Unless you live in like Bumstump, TX where you can buy a 4 bedroom 3 bath home on 2 acres of land for 60k.

A proposal, which was a PETITION, made by interns, that have absolutely no capital with which to bargain, let alone demand via petition, over the company's culture. It's insane.

There is a big difference between an open-door policy and allowing a group of interns, most of which are a net-negative for the company while they are interns, to petition the company's leadership to change their culture. The intern writing the letter even stated that they had already had a conversation with their manager about it. Sounded like that convo went pretty well. "We appreciate your view, but no, the dress code is not changing". That is a good open door sounding culture.

"Special Snowflake" is pretty fitting here. You want to band together with fellow interns to make changes at the company with which you are interning? Make that company some money. That's why they are in business. That's what they will listen to. You are a "Special Snowflake" if the dress code is the sword you are going to fall on. It's nuts and these kids need to grow up.

Banding together with other interns and petitioning the company to change their culture is crazy levels of naive. As an intern, you are most likely a net-negative. At best, consider yourself on a long term interview. It's not the time to ask that the company change its culture. If you happened to get picked up by the company and find yourself in a job, it's still not the time. It's not a democracy. The business was built to make money and it was determined long before you got there that the dress code would help them achieve that goal. Unless you can put some money where your dumb petition is, your best hope is some extreme eye rolling.

The world is full of simplified programming languages. The problem with newb adoption isn't just a function of ease-of-use, the simple programming language must also interact with a familiar UI. Why would I, as a newb, want to write in a simple programming language if it can't do something sufficiently complex, like create form UI, or change a web page, or interact with my OS to do something useful?

This is why VBA is so common. It's a simple scripting language that is exceedingly forgiving and interacts with a built in UI that most folks are already comfortable using. There is a "Macro Recorder" that writes the script for you if you wish. As you advance in your VBA skills you can interact with other VBA enabled applications on your machine and then graduate to shared libraries and com objects and interact with the OS. Furthemore, Microsoft Office applications come with a built in IDE (VBE), so you are ready to go, out of the box.

Hardy har har

I don't know where I stand on this one. Museum Hack seems overly protective of their pretty generic name. T&L either employs a lazy designer or a vindictive writer. None of the offenses seem legal-worthy, so really it's just a morality thing. Right?

Final Verdict: Museum Hack by a hair! Since I'm nobody, you only get 5 points this round. I can't tell if ya'll are just going for publicity with this or you're just really attached to primary colors. Whatever though, it's business.

That website has gained R/W access to my brain. It uses pointers and had to be compiled with /unsafe. It compelled me to write this comment. I've lost control of both my pointer fingers, my left big toe, and my left eyelid. Why would God sign this s,ǝʇᴉsqǝʍ code when it uses bits of code from 100BC that were written before Jesus came and locked down sin. Probably code ƃuᴉuƃᴉs a̷̶̙̫̳͔͂͗̋̃u̜̍͒̔̅͛ͪ͘t̪̞̠̃̆ͯ͛̓̓ǒ͎̹̺͉̚̕͟͡m̺͔̞͉̦͓ͧͥͤ͛̅́͞a̛̫͉̹̒ͨ̏͜ẗ̵͎̖̻̺̤̱̰̹̯̕͡i͓̬̲̅ͮ͢͡ỏ̷̯͔ͪͯ̄ͅń̡̖̭͚̹͚̪̊̃͌́̚ ̟̳̤̩͉̭͓̀̓̈̍̔͝w̛̘̱͚̫̉ͬ͗ͯ̒̽͂ͭḩ̡͍̖̻͗̊͒̾̈́̐ͯi̠̼͒̇̄͛ͣ̀̀c̹̝̞̀̽ͤ̓̃̚h̘̪͙ͭ͛͆ͥ̓ ˙ƃuᴉɯɐǝɹɔs ǝɥ┴ ˙ƃuᴉɯɐǝɹɔs ǝɥʇ uᴉɐɹq sᴉɥʇ ɟo ʇno ʇuɐʍ I ƃ̮͚̳̮̻̗͝u̪̺͎̘͎͚ᴉ̫͇̫̮̲̗ɯ̴̤̥̠ɐ̪̠̻̳͔̭ǝ̬ɹ̲͚̗̣̟̳ɔ̛̺͔̯̖̯s̝̜̫͘ ̴͉̱͎̭̯͇ǝ̖̝͎͎͇̞̙͟ɥ҉┴͙̣̞̞̜͎͇͟ ̙͉̠͖̩̭ͅ

Woah.. like there are even easter eggs in there. That's not what I expect when I use that color code. Also, are you high?

Hacker News Commentor Blasts WSJ's Paywall in Short Comment: pw;dr

That's my concern though. When you look at other enterprise-sized RDBMS you find tight integration at the "machine" level. Oracle's storage, for instance, uses "Blocks" which are sized based on the block size of the disk they are writing to. This tight integration at such a low level is part of what makes these RDBMS's fast. I would imagine that instead of running on an abstract layer that can be commonly built across many OS's that an RDBMS like Sql Server would be more tightly integrated with the machine they are running on in order to maximize performance and disk space. If so, I would really love to dig through what that means for SQL server.

At the end of the article (although it's not stated, and the link was down about when this was posted): https://www.microsoft.com/en-us/server-cloud/sql-server-on-l...

Doesn't EF just use an ODBC connection? I can't imagine that the OS upon which the Server is running would have any effect on something as high up the stack as ODBC/OLEDB.

I'd like to know more about this too. Data storage and retrieval is such an important and integral part of an RDBMS and the switch to Linux suggests that they've had to tear up a lot of their low-level logic. How well they've done optimizing storage for EXT3/EXT4 seems to be pretty important. It would be interesting to see what's changed and how they managed this.

I will agree with you on that one, but one is free and the other isn't. Postgres, however, is free and blows MySQL out of the water. Each has their pros and cons though.

SQL Server on a virtual Windows server is like the de facto set up within the non-IT-but-still-kind-of-technical groups of large organizations. There's just a ton of UI tools built for it and it's a nice transition from Access to something more robust.

But it means having a separate windows-server team set up to handle builds and all that. The crappy thing is that the rest of IT uses Linux or Unix based OSs for their software, so Cygwin ends up getting installed on most Win Servers to open them up to the NFS shares that drive most of the data movement. I could see this being pretty huge to be able to migrate the various SQL server versions and Win OS versions over to Linux and ditch the need for dual environments while still supporting a RDBMS that most of the business is comfortable using and has tons of legacy data and apps built against them.

But.. yea I agree. If you just need a database, drop Postgres on a linux box and role. It's free and there is a huge community. If you've got the money and need something managed for you with support built in and lots of horsepower then go with something like Teradata. SQL Server feels like the Sears/k-mart of RDBMS. I'll just go to Walmart, thank you very much.

Does the author also not own a television? What did the author think of older cell phones since the same argument applies? The same arguments have applied long before smart phones as well. Did the author not like CD players? Perhaps he/she railed against newspapers too.

The first argument is based on a terrible premise that only exists to support authors decision to not have a cell phone.

The second argument is just as pitiful as clients have nearly always been centralized. Just because your favorite protocol isn't used often on the device doesn't make this terrible argument stand up.

The third argument... I can't even remember what it was because it was stupid, or perhaps my eyeballs rolled so far into the back of my head that I wasn't able to read anymore.

That poor little web server at the link. Talk about "Crash and Burn". The Cat5 cable connecting it to its network are probably melting. It's OK little web server! You can do it! Just keep trying!

And MySQL is still a poor choice.

Bravo! How have I never read this article. Every single one of these points, plus:

1) It's INSANE handling of GROUP BY. In any other RDBMS, a GROUP BY that is missing non-aggregated fields in the result set of the query would throw an error, but MySQL just lets it fly defaulting to some random ass behavior that will return garbage 100% of the time.

2) It was mentioned that it lacks Windowing Functions, which is a HUGE miss, but it also lacks native Recursive Views. The workaround is some horrid mess of self referring variables. Why Recursive views, a T-SQL standard that is in nearly every other adult RDBMS, is lacking here is beyond me. (I know it's not a T-SQL standard database by design, which is just another nail in it's coffin if you ask me.)

I was just reading through a very lengthy StackOverflow question where the poor schmuck was trying to migrate from MSSQL to MySQL to save money. Noone at her shop, including her, had heard of Postgres. It's free. It's been around a hell of a long time. There is a huge community that uses it. And it's T-SQL based. It's just 100% better.

MySQL is some Kool-Aid that we should all just put down and back away from.