Answer: no one cares
Why is this Go faster than the equivalent Java?
11–20 of 105 posts
Re: Why is this Go faster than the equivalent Java?
#12I love this sort of post, and it makes me miss programming (i'm a Linux sysadmin type now) The golden age of this stuff was when I was writing stuff for the Atari ST and Amiga. Fixed hardware, manuals that came with assembly instructions and timings, etc. My greatest moment was when rewriting the Atari ST text output function. For those that don't remember, the ST had an interleaved bitmap [1] and no hardware blitter…
How is that working out for you? Isn't the pay significantly less being a sysadmin?
Re: Why is this Go faster than the equivalent Java?
#13I love this sort of post, and it makes me miss programming (i'm a Linux sysadmin type now) The golden age of this stuff was when I was writing stuff for the Atari ST and Amiga. Fixed hardware, manuals that came with assembly instructions and timings, etc. My greatest moment was when rewriting the Atari ST text output function. For those that don't remember, the ST had an interleaved bitmap [1] and no hardware blitter…
[deleted]
Re: Why is this Go faster than the equivalent Java?
#14I love this sort of post, and it makes me miss programming (i'm a Linux sysadmin type now) The golden age of this stuff was when I was writing stuff for the Atari ST and Amiga. Fixed hardware, manuals that came with assembly instructions and timings, etc. My greatest moment was when rewriting the Atari ST text output function. For those that don't remember, the ST had an interleaved bitmap [1] and no hardware blitter…
How is that working out for you? Isn't the pay significantly less being a sysadmin?
It's illusory to think that we have a choice. It's hard to avoid becoming obsolete over a long timespan.
Re: Why is this Go faster than the equivalent Java?
#15Earlier quoted context omitted.
How is that working out for you? Isn't the pay significantly less being a sysadmin?
It's illusory to think that we have a choice. It's hard to avoid becoming obsolete over a long timespan.
I am a bit confused about what you are referring to. Are you saying that we do not have many choices when it comes to work? I am about to graduate, but a lot of people seem to be saying that once you gain experience it is easy to hop to different jobs.
Re: Why is this Go faster than the equivalent Java?
#16Than
THANKYOU. Drives me nuts when people mess that up.
Re: Why is this Go faster than the equivalent Java?
#17I love this sort of post, and it makes me miss programming (i'm a Linux sysadmin type now) The golden age of this stuff was when I was writing stuff for the Atari ST and Amiga. Fixed hardware, manuals that came with assembly instructions and timings, etc. My greatest moment was when rewriting the Atari ST text output function. For those that don't remember, the ST had an interleaved bitmap [1] and no hardware blitter…
How is that working out for you? Isn't the pay significantly less being a sysadmin?
No, it's better. I basically got burned out writing the same code for 5 different financial companies so tried something new. Loved Linux, loved the CLI, loved the power it gave me. I've literally saved a startup when paged in a nightclub at 3am and having to type very carefully to fix their database replication.
You need to pivot in work, especially as most of us will be working for 40 years+. I'm getting into the security stuff now, which I think is the new hotness.Only thing bringing me back to programming is golang which is absolutely superb for server-side stuff.
Re: Why is this Go faster than the equivalent Java?
#18Earlier quoted context omitted.
How is that working out for you? Isn't the pay significantly less being a sysadmin?
It's illusory to think that we have a choice. It's hard to avoid becoming obsolete over a long timespan.
It's illusory to think that we have a choice. Engineers are "dev-ops" now and sysadmins are "site reliability engineers." Everybody has to do everything.
Re: Why is this Go faster than the equivalent Java?
#19Earlier quoted context omitted.
It's illusory to think that we have a choice. It's hard to avoid becoming obsolete over a long timespan.
I am a bit confused about what you are referring to. Are you saying that we do not have many choices when it comes to work? I am about to graduate, but a lot of people seem to be saying that once you gain experience it is easy to hop to different jobs.
[deleted]
Re: Why is this Go faster than the equivalent Java?
#20Earlier quoted context omitted.
It's illusory to think that we have a choice. It's hard to avoid becoming obsolete over a long timespan.
It's illusory to think that we have a choice. Engineers are "dev-ops" now and sysadmins are "site reliability engineers." Everybody has to do everything.
I do hate the 'devops' prefix. It's used indeterminately by everybody unfortunately, including at a recent client that didnt have devs. It's job title inflation, a bit like calling somebody a barista because they press the coffee button.