ibiza
ibiza on Hacker News
I think that is being too charitable. The problem is 100% reproducible. The machine blue-screens at boot up. What kind of staging environment allows this to go through?
I wonder if a Sun, Dec, or HP of the 90s would have had a fighting chance against Windows NT had they not embraced X, and instead developed a local-first stack optimized for their considerable hardware.
Related, I've always found it odd that in Linus' history of Linux, part of it was a desire to implement an Amiga-like OS on a PC. This is the message-passing-bad guy. What happened?
I did not realize cd'ing up was an esoteric sport. My own take:
shopt -s cdable_vars
u2=../.. u3=../../.. u4=../../../.. u5=../../../../..
HAL 9000 is already included as z/OS or z/VM.
§3.1 Timely rejection is key. Ghosting a candidate as a sign of no-move-forward is beyond crass.
The PC (1981) predates the first color 3270 terminals like the IBM 3179 (1984). A 3179 had 7 colors: pink, red, blue, yellow, green, white, and turquoise. I used one & remember it looking quite good but different from PCs of its day.
Re DB2 vs UDB, thank you, it's been too long. Well done breaking DB2!
We actually targeted Oracle on Unix. Fortunately, the app developers never got too deep into DB2-isms, so it worked out fine.
The env I helped set up was online only, no batch jobs. JCL is essentially a declarative shell language, so it's not that hard to map to Bourne shell et. al.
Migrating a suite of programs written w/ COBOL, CICS, DB2 from z/OS to Linux is fairly straightforward. MicroFocus COBOL compiles IBM COBOL, DB2 runs on Linux or you can swap out another RDBMS. The CICS part requires a simple runtime easily implemented in C plus a new scanner to replace the calls in your programs.
I was part of a 4 person team that knocked this out in under a year. 1,000's of mainframe programs running w/o change (at the time) on Unix. This was in the 90s.
I find the bifurcation between HTML elements and CSS statements maddening. Structural things like flexbox and grid would be far clearer as HTML element types.
Same. Outside of Lisp & some shell, you've got the OG Cobol and Raku. HTML attrs? CSS? It's a shame really. So easy to type and read.
I'm happy one can buy a mighty 4-stack RPN calculator today new. Greedily, I wish they had recreated the 32S instead, as it had a single Gold function key and far less busy silk screening. I say this as a former owner of a 32SII.
https://www.hpmuseum.org/32s.jpg
Your point stands, but I think you're arguing about static vs dynamic typing, rather than strong vs weak typing.
CL is dynamically typed (values have types, not variables), w/ strong types (automatic type coercions are rare).
That's a a compelling argument: GC/RC w/ stack allocation where possible. I associate GC w/ pointer chasing and the unavoidable L1, L2, L3 cache trashing that goes w/ it.
To what extent is this possible? Does Nim have LTOs that rewrite memory handling across compilation units? I'm guessing no, and instead it's local & one-off, rather than something one can bank on.
> call it a day, finish work early and go to the beach for sunset.
That's great, except if you're on call, responsible for your own and your team's code. Hopefully, there are no NullPointerExceptions, ConcurrentModificationExceptions, not to mention the odd race condition or two. I appreciate a language that can eliminate the majority of these cases at complie time. I'd rather sort these issues out on a Tuesday morning than get pulled off the beach by PagerDuty.
Those are great points. Generalizing a bit:
* Identify your superpower
What special mojo do you bring to a problem that no one else on your team can? Recognizing and leveraging your superpower can make running w/ a team of true overachievers a lot more pleasant.
> a big chunk of these vulnerabilities would not exist if C and C++ [...] simply didn’t have zero-terminated string, initialized values by default, had a proper pointer+length type thus replacing 90% of pointer arithmetic with easily bounds-checkable code, and had established a culture that discouraged the prevalent ad-hoc style of memory management.
This is Rust's calling-card, so I find this plea for a better lang / eco rather jarring after dismissing Rust for somehow "making the wrong tradeoffs".
Is there potential for a Erlang -> Elixir play here? Ada -> Grace :). I find it a shame languages w/ a Pascal lineage are unpopular simply for syntactic reasons.
