|
Not surprising that GO beats .NET Core, as GO is a compiled language. I'm tempted now to try GO.
Beware though that GO is not really suited for creating rich user interfaces.
|
|
|
|
|
The tests aren't "real" enough because they are all run in memory. IMHO, the test programs should do some "hard(ware) IO", like reading from a disk file, doing network data exchange, etc., to see the differences. This is the area where .NET Core could shine due to its "async" support of overlapped IO. Java and Go do not have such a support as far as I know (maybe I am wrong since I know very little about both).
By the way, "overlapped IO" is not limited to Windows, Unix family of OS has "epoll" to support it ...
|
|
|
|
|
The shiny newness of life in the workforce begins to wear off. Sorry, 34-year olds that like their jobs
|
|
|
|
|
|
bloomberg wrote: People start hating their jobs at age 35
What took them so long?
|
|
|
|
|
Not "age 35" but 08:35 in my experience.
|
|
|
|
|
Exactly!
TTFN - Kent
|
|
|
|
|
I start at 0700 so it's a little earlier for me.
|
|
|
|
|
If I'm, apparently, liking my job now (not 35 yet) then whence cometh hate?
|
|
|
|
|
By 35, you're probably realizing your life is likely 1/2 over, and what have you done besides being a legal slave? And yeah, the mid-life crisis thing already mentioned.
|
|
|
|
|
For most people in the Western World, their adult life has barely started at age 35:
Ages 0..18 - minor
Ages 19..22 - college (not real life)
Ages 22..65 - work
Ages 66..78 - retirement
By my calculation, they have lived 13/56 (or less than 25%) of their adult lives, and 13/43 (less than 33%) of their working lives. This gives them plenty of time to change careers, should they feel the need.
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
Google Enterprise offers enterprise mobility management and supports Microsoft Active Directory. The aim is to put more Chromebooks in companies. All the joy of VT100, with added advertisements!
|
|
|
|
|
Don't forget the double data security. If you get a data loss and you ask nice enough, you might get your data back from them
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
There are countless jobs in software development and software engineering. But what’s the difference and which one are you best suited for? I'm a software "bang my head on the keyboard"-er
Mind you, I haven't done that much JavaScript lately
|
|
|
|
|
You've done it, now I'm confused
|
|
|
|
|
When I was growing up the difference was that a software engineer was someone who worked closely with hardware while a developer was higher level. But meanings change. Not sure I agree with the given difference, both engineer and developer should be asking questions and "why?".
#SupportHeForShe
Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
|
|
|
|
|
...a developer takes functional specification and delivers the code required within tight parameters, essentially completing the task in isolation, without understanding or oversight of the project as a whole,
In other words, a code monkey. While that can work in certain situations, there's usually a canyon between "coding within tight parameters" and code that actually does what's really needed, because...
...an engineer is someone who thinks about the design, goes back to the business with questions and suggestions, and thinks about the impact on the business and the end user
The engineer will not get it 100% right. The only way to get it "right" is to have a back and forth dialog -- "hey, I know you said to do X, but there's problems with that and I think doing X' would be better."
Ironically, the author himself discovered that:
Everyone was involved in the full life cycle of the product and they were encouraged to have a solid understanding of why we worked the way that we did...Upon his return to Ireland, O’Donnell took up his former role as a programmer but had a different mindset about the job.
The moral of the story? Labels are meaningless. The more you know and involve yourself, the better off everyone is. Which is why, when mentoring people in even something as supposedly straight forward as the C# language, I always include the big picture and the tradeoffs in something even as nuanced as var i = 5; vs. int i = 5;
Marc Dang, I did it again. I'm trying!!!
modified 23-Aug-17 8:16am.
|
|
|
|
|
Yeah, no.
It's the same with all engineering. The main thing is the cost of a failure; whether or not you get do-overs.
If it must be right the first time and every time; that's engineering.
Line-of-business applications, Web applications, etc. are never engineering regardless of the qualifications and attitude of the developer(s).
|
|
|
|
|
|
As general counsel for an open source and commercially licensed software company, I have been asked by hundreds of customers to review their use of open source software (OSS) and compliance with licensing terms. Free as in puppy (that needs lots of newspaper)
|
|
|
|
|
Yeah, but on the other hand, all those OSS creators don't have any money to hire a lawyer to sue you for license violations.
(ok, someone will prove me wrong no doubt.)
Marc
|
|
|
|
|
We posted earlier today that the ISDA Award-winning Microsoft HoloLens Mixed Reality headset was out of production, and was surprised that this news surprised our readers, assuming it was common knowledge. It was in production?
|
|
|
|
|
Intel might be sticking to the familiar Kaby Lake architecture for the eight generation of its Core chips, but the its internal testing looks pretty promising as far as performance goes. I'll believe it when I see it. Please send a bunch for testing.
|
|
|
|
|
That's not entirely fair though, they've stuck more cores on those chips.
Meanwhile there is also the less-unexpected headline "Intel Confirms Core i7-8700K Coffee Lake Single-Threaded Performance 11% Faster Than Kaby Lake 7700K"
|
|
|
|
|
Good, I need to upgrade from Core 2 some time soon maybe ...
Intel® Core™2 Quad Processor Q8200
Intel® Core™2 Duo Processor E6850
|
|
|
|