HN user

Sean1708

1,208 karma
Posts0
Comments694
View on HN
No posts found.

As other top-level posts have pointed out they're only removing it from the build process, it's still available to users. I wouldn't worry too much about about GCC going away, it's still the default compiler for most (all?) Linux distros.

Somehow this works even across SSH connections…

The source code[1] is quite simple to read (as long as you know Bash) but basically imgcat prints a special OSC[2] sequence (some bytes that tell the terminal to do something special) to stdout followed by the image data which iTerm then handles specially because of the OSC sequence, as far as SSH knows they're just some bytes that it needs to send (no different than running normal cat on a text file). You can kind of think of this as the opposite of what bracketed paste[3] does, in bracketed paste the terminal tells the program to treat some data specially but with imgcat the program tells the terminal to treat some data specially.

[1] https://iterm2.com/utilities/imgcat

[2] https://en.wikipedia.org/wiki/ANSI_escape_code#Escape_sequen...

[3] https://invisible-island.net/xterm/ctlseqs/ctlseqs.html#h2-B...

an incomplete microservice migration where you've now got hobbled together half-service weirdware that you have to support forever.

Ugh I have to deal with this at my current job, except it's not an incomplete microservice migration it's by design and comes with a weird hobbled-together event queue implemented as a table in the DB and that has a known race condition that pops up every couple of weeks.

what is the benefit of the line format being character strings? Wouldn't a binary package not be just as easy translatable into human readable JSON formatted output as a compacted JSON string is?

One benefit is that I can look at an arbitrary file/response and be able to tell with a fairly high certainty whether it's JSON, YAML, or TOML, but there's no way that I tell whether it's messagepack, bson, or protobufs.

I think it's a lot more complicated than that. Yes there are plenty of people that use Docker as a package manager, but I think that's a failing of traditional package managers rather than a failing of Docker. You could, for exactly the same reasons, say that Nix is Nix Containers[1] Done Right but if that were true then Nix Containers wouldn't need to exist in the first place.

[1] https://nixos.org/nixos/manual/#ch-containers

If I can reduce my entire desktop environment into a single config file and have it reliably reconstruct itself, it would be magical.

I might be missing something, but it sounds like that's what home-manager[1] was designed to do. Certainly works pretty well for me.

[1] https://github.com/rycee/home-manager

I actually did some benchmarking on this once upon a time[1] and it turns out that it's actually really easy to write something that is only ~5x slower[2] (until you get to matrices that don't fit in RAM):

           (4, 4, 4) (5, 5, 5) (32, 32, 32) (33, 33, 33) (256, 256, 256) (257, 257, 257) (512, 512, 512) (513, 513, 513) (1024, 1024, 1024) (1025, 1025, 1025)
  –––––––– ––––––––– ––––––––– –––––––––––– –––––––––––– ––––––––––––––– ––––––––––––––– ––––––––––––––– ––––––––––––––– –––––––––––––––––– ––––––––––––––––––
  :naive         0.0       0.0       1.3e-5       2.0e-5          0.0114          0.0133          0.0942           0.106               3.25               2.39
  :tiled         0.0       0.0       2.7e-5       2.2e-5          0.0139          0.0121           0.154           0.101               1.25              0.888
  :fastf77       0.0       0.0       8.0e-6       8.5e-6         0.00543         0.00563          0.0426          0.0445              0.437              0.448
  :blas       4.5e-6    4.0e-6       1.9e-5       2.1e-5        0.000972         0.00109         0.00712         0.00744             0.0582             0.0607
(Units are seconds per multiplication.)

Obviously OpenBLAS is so easy to package that it's not really worth avoiding it, but it was very eye-opening to see just how easy it is to get within an order of magnitude (easier, in fact, than getting into the 10x-20x range).

[1] https://gist.github.com/Sean1708/69c5694048e9a9ca7bd84fcbc9e...

[2]: 8-core 3.4GHz Haswell i7 with 32kB L1, 256kB L2, 8MB L3, and 8GB RAM.

My main issue with it is that if someone figures out an even better way to do dictionaries but it doesn't preserve insertion order, then that technique can't be used. But I certainly wouldn't call it a stupid decision, the problem is that once a behaviour is observable then people absolutely will start relying on it.

It is but in the context of this discussion it's very clear that they meant a tracing garbage collector, which has a very different cost than atomic reference counting. Or to put it another way: you're technically correct, the worst kind of correct.

Nah, it's true for all columns:

  SQL*Plus: Release 11.2.0.4.0 Production on Mon Feb 3 15:56:30 2020
  
  Copyright (c) 1982, 2013, Oracle.  All rights reserved.
  
  
  Connected to:
  Oracle Database 11g Express Edition Release 11.2.0.2.0 - 64bit Production
  
  SQL> create table foo(fook varchar2(10) not null);
  
  Table created.
  
  SQL> insert into foo values ('');
  insert into foo values ('')
                          *
  ERROR at line 1:
  ORA-01400: cannot insert NULL into ("SPORTSBOOK_DOCK"."FOO"."FOOK")
  
  
  SQL> create table bar(bark varchar2(10));
  
  Table created.
  
  SQL> insert into bar values ('');
  
  1 row created.
  
  SQL> insert into bar values ('a');
  
  1 row created.
  
  SQL> insert into bar values (null);
  
  1 row created.
  
  SQL> select * from bar;
  
  BARK
  ----------
  
  a
  
  
  SQL> select * from bar where bark = '';
  
  no rows selected

AFAICT there's no easy way to measure the LoC actually compiled

I take it you can't just run it through the preprocessor then count the lines of code that are output from that?

Let's Destroy C 6 years ago

Firstly, I think you're taking this waaaayyyy more seriously than it was intended. Secondly

  double foo = 1.2;
  printf(foo);
  puts(foo);
won't compile, while
  double foo = 1.2;
  display(foo);
works fine.

Incidentally I actually think display is the only thing on this list that is probably worth using, you could also probably extend it to accept multiple arguments relatively simply as well.

That sounds like an example of it being exactly like this (since neither Go nor C++ have had any breaking changes either AFAIA), or am I not understanding something?

I strongly believe that the biggest reason people struggle with the Magic Roundabout is because it's called a roundabout, when it's actually just a collection of 5 roundabouts. If you tackle it one roundabout at a time it's actually not that bad at all, it could be much much better, but it's not bad.

But equally something being fun or worth doing doesn't mean you won't procrastinate doing it. Cleaning the house, for example, is definitely worth doing but many people procrastinate doing it, and it's actually a really good time to apply this technique:

You don't have to clean the whole house, you can just clean one room. You don't have to clean an entire room, you can just clean a bookcase. You don't have to clean the entire bookcase, you can just clean one shelf. You don't have to clean the entire shelf, you can just put one thing back in it's place. You don't even have to put it back, just go over and pick it up. ...

You can keep on going if none of those seem doable, right down to something like wiggling your big toe, but most people would probably at the very least find putting a single thing back doable.

And I've used an example of something that is worth doing but most people don't find fun, but there are plenty of examples of things that are both fun and worth doing that people still procrastinate (probably mostly occurs in mental health sufferers, but that was the entire point of my original comment).