Golang.......nice language, but it has some braindead parts. Instead of using make(), they could have just used new like every other datatype. No need for a specialized function. map.New() would have been completely acceptable, and more consistent.
The keyboard input is braindead. There are a lot of functions, but they combine the archaic-ness of C with the verbosity of Java. fmt.Scanln() doesn't actually read a line, it reads a word (delimited by spaces). Reader.ReadString('\n') is recommended in the documentation, but that is probably useless because it doesn't read the final line if it ends with EOF instead of a newline. I've been trying to think of a situation where that is even useful.
Concurrency in Go is nice, but go routines are just threads. Message queues are a nice way to solve some of the problems of shared memory, but you have to think about deadlocks every time you use one because they are blocking.
Maybe. This article doesn't make a very good case for it, though. He's claiming the C++ syntax for doing a callback is easier than the C syntax. His example syntax doesn't look much better, though.
What particularly don't you like about C syntax? I've always thought that the main security problem with C are caused by the lack of a decent buffer processing library, and a lousy string processing library. Fix those two things (and any person can do it in their own code!) and you've fixed the vast majority of C security bugs.
I just placed a hold on the book at my local library. It will take a bit of time for me to get around to it, but if you ask in a week or so I should have something more informative to say on the topic.
The standard still isn't released, and won't be released until 2018. The actual RAM might not make it here until 2020.
The main news (afaict) is that DDR5 will have double the bandwidth of DDR4. It's also going to have lower power requirements yet, and since the standard hasn't been finalized yet, grant you a pony.
Unfortunately for Twitter, there doesn't really seem to be a good way to monetize it.
Which is to say that they can make $700 million in revenue, which is more than enough to sustain operations, but they can't match Facebook or Google money.
I spent a couple years doing ASP.NET back in its heyday. I thought it was an over-engineered curiosity. Things like replacing standard HTML elements with ASP specific tags seemed bizarre. It sent so much data back to the server on every request that it felt bloated and wasteful.
But now.......compared to many popular frameworks, with whole pages written in Javascript (or non-standard JSX), or the bloated mess that is Angular, it seems positively genius. The <UpdatePanel> thing made Single Page Apps easy, long before Node.js was a thing.
The sad thing is that Microsoft has drunk the coolaid. Internally some of their teams are moving away from ASP.NET, and are going with Javascript frameworks. EntityFramework is dog slow, and while C# is a fine language if you like the Java family of languages, it's still has the feel of being a COBOL replacement (much like Java). They are all built for the same purpose.
Nginx wasn't around when the website was created.
It doesn't matter how secure your OS is if you're running a vulnerable web server. If you open telnet on OpenBSD, you can consider yourself pwned. Nginx has a better record that IIS, but you know, it's not perfect. Maybe you can run a proxy in front of it to defend against security vulns.
It seems too obsessive to me. Twitter let's you follow who you want. If you don't want to follow liberal people, then don't. I don't follow Donald Trump, and I don't complain when he tweets. I don't even know it. Twitter also gives you tools to block whoever you want, so if liberal or conservative people annoy you then you can deal with it. To me the whole question is about as relevant as whether there are more people that like pumpkin pie or hate pumpkin pie on Twitter. I don't understand those people, but you know, I either forgive them or ignore them.
I think the point is to encourage other artists to record so they will make the money the Beatles are now making. Of course the Beatles are a bad example since they don't own the copyright on most of their songs.
Because somebody thinks that HTML belongs wrapped in Javascript.
Yeah, that is an idea that makes little sense.
C++ isn't safer than C, it gives you a bazooka to blow your foot off.
Golang.......nice language, but it has some braindead parts. Instead of using make(), they could have just used new like every other datatype. No need for a specialized function. map.New() would have been completely acceptable, and more consistent.
The keyboard input is braindead. There are a lot of functions, but they combine the archaic-ness of C with the verbosity of Java. fmt.Scanln() doesn't actually read a line, it reads a word (delimited by spaces). Reader.ReadString('\n') is recommended in the documentation, but that is probably useless because it doesn't read the final line if it ends with EOF instead of a newline. I've been trying to think of a situation where that is even useful.
Concurrency in Go is nice, but go routines are just threads. Message queues are a nice way to solve some of the problems of shared memory, but you have to think about deadlocks every time you use one because they are blocking.
"=" vs "==", the presence or absence of commas or semicolons that substantially change meaning, the mess that is #include in large systems...
Those types of bugs are very rare, and #include was solved long ago with #IFNDEF _HEADER_NAME....
Maybe. This article doesn't make a very good case for it, though. He's claiming the C++ syntax for doing a callback is easier than the C syntax. His example syntax doesn't look much better, though.
What particularly don't you like about C syntax? I've always thought that the main security problem with C are caused by the lack of a decent buffer processing library, and a lousy string processing library. Fix those two things (and any person can do it in their own code!) and you've fixed the vast majority of C security bugs.
With a halfway decent macro library, assembly's not too bad.
And UpdatePanel didn't show up until 2007? seriously? Guess we were ahead of our time
I don't think any other framework has something like that, but maybe I'm wrong.
I just placed a hold on the book at my local library. It will take a bit of time for me to get around to it, but if you ask in a week or so I should have something more informative to say on the topic.
The standard still isn't released, and won't be released until 2018. The actual RAM might not make it here until 2020.
The main news (afaict) is that DDR5 will have double the bandwidth of DDR4. It's also going to have lower power requirements yet, and since the standard hasn't been finalized yet, grant you a pony.
Heh, your reading comprehension is bad, but I'll give you a hint:
The earlier comment you replied to included the words "excluding...." You obviously didn't read that sentence to see what was excluded.
I'll put an unpatched Netware 4.12 server **directly on the internet**
That's a good idea. No one will know how to hack into it over IPX.
Unfortunately for Twitter, there doesn't really seem to be a good way to monetize it.
Which is to say that they can make $700 million in revenue, which is more than enough to sustain operations, but they can't match Facebook or Google money.
If you're thinking pre-MVC web forms
No.
Think if you could swap any of those components to their 2003 counterpart. Would it still work?
Apache sure would.
Nope. It's probably in the library, maybe I should look it up.
I spent a couple years doing ASP.NET back in its heyday. I thought it was an over-engineered curiosity. Things like replacing standard HTML elements with ASP specific tags seemed bizarre. It sent so much data back to the server on every request that it felt bloated and wasteful.
But now.......compared to many popular frameworks, with whole pages written in Javascript (or non-standard JSX), or the bloated mess that is Angular, it seems positively genius. The <UpdatePanel> thing made Single Page Apps easy, long before Node.js was a thing.
The sad thing is that Microsoft has drunk the coolaid. Internally some of their teams are moving away from ASP.NET, and are going with Javascript frameworks. EntityFramework is dog slow, and while C# is a fine language if you like the Java family of languages, it's still has the feel of being a COBOL replacement (much like Java). They are all built for the same purpose.
Nginx wasn't around when the website was created.
It doesn't matter how secure your OS is if you're running a vulnerable web server. If you open telnet on OpenBSD, you can consider yourself pwned.
Nginx has a better record that IIS, but you know, it's not perfect. Maybe you can run a proxy in front of it to defend against security vulns.
You can go rather quickly on some modern gams, too
Weird, I was planning on getting it entirely based on whether or not the games were fun.
It seems too obsessive to me. Twitter let's you follow who you want. If you don't want to follow liberal people, then don't. I don't follow Donald Trump, and I don't complain when he tweets. I don't even know it. Twitter also gives you tools to block whoever you want, so if liberal or conservative people annoy you then you can deal with it. To me the whole question is about as relevant as whether there are more people that like pumpkin pie or hate pumpkin pie on Twitter. I don't understand those people, but you know, I either forgive them or ignore them.
Why do people care so much about this topic?
Did you read the book? That's kind of the point of the book.
To add to your point, the law is so complex that the average person might commit three felonies a day, even though they did nothing wrong.
I think the point is to encourage other artists to record so they will make the money the Beatles are now making. Of course the Beatles are a bad example since they don't own the copyright on most of their songs.
Twitter: Yeh. Stupid cow, what the fuck was she talking about?
It's ironic you say that, since of all the companies you listed, Twitter has made the strongest efforts towards not disrespecting women.