You're replying to an LLM.
HN user
cgdub
I don't write Perl or Ruby anymore, but this would have been immensely helpful back then.
If you sort by Issues, C++ is #3 and trending up.
We’ve had Lisp for 60 years, but instead of using that, we’re going to have LLMs write the boilerplate for us.
You will still have to read the boilerplate of course.
I think Rob Pike would agree that "smart objects" is the wrong way to think about it: https://commandcenter.blogspot.com/2012/06/less-is-exponenti...
They do this so they can show more commercials to people watching the game on TV.
Of course it makes watching the game a worse experience.
I work in a large code base where we've told all of the developers to use dependency injection frameworks.
We are now using a mixture of 3 different dependency injection frameworks, manual dependency injection, and instantiating dependencies in the constructor.
The future of the web is web developers creating more work and thus more jobs for web developers.
It's the same reason Java, with all its boilerplate, is so widely used.
ClojureScript already compiles to CommonJS with the built-in :target :bundle option.
We have rules around changing the schema. You can only add new fields and deprecate old fields. You can't rename or reuse fields. All new fields must be optional to make schema evolution possible.
In practice, this is pretty similar to how you maintain compatibility with old clients in JSON. But with protobuf, you have the schema file to make code reviewing this kind of change easier.
"Quiet! The commercial's on! If we don't watch these, it's like we're stealing TV."
There is public housing in NYC, and I can assure you that your landlord is better than NYCHA.
No one needs to know about distributed systems until your company wants to send automated emails to customers and someone thinks all requests need retry logic.
NYC already has rent control. It's why rents are $5k.
A tool or technology that adds work is extremely useful.
More work means
- more employees needed
- more direct reports for managers
- more jobs for x technology
- more people learning x technology because of those jobs
- more StackOverflow questions for x
- more companies using x technology because it's "easy to hire for"
- more money to be made in teaching x
- more learning material for x
Thousands of classes with indirection is absolutely Clean Code. It's in the book.
I use a gaming monitor with an inoffensive design and a monitor arm. You can't easily tell that it's a gaming monitor because I'm not using the ugly stand that came with the monitor.
Does that mean you would get paid less for living in Queens County instead of New York County?
The factory is expanding to meet the needs of the expanding factory.
DCEVM
If you use a sufficiently smart JS optimizer, it will optimize the object creation and destructuring away.
For example, Google Closure Compiler can take
function hello({name}) {
alert('Hello, ' + name);
}
hello({name: 'World'});
and compile it into alert("Hello, World");In a similar vein, `React: CSS in JS` from vjeux: https://blog.vjeux.com/2014/javascript/react-css-in-js-natio...
Make your alt keys do control, your win keys do alt, and your control keys do win.
No more Emacs pinky.
Unless there's been a large rewrite, it's likely Closure Library: https://developers.google.com/closure/library
A single canal is a single point of failure. We need to have multiple canals to handle unexpected failures.
I have found myself in a similar role and lead a team that spends most of our time improving the front-end build tools and front-end testing infrastructure that all teams in the company use and splitting the company's codebase into micro-frontends where it makes sense.
Depending on the company and product, it might make sense to focus on performance or building a shared component library. In our case, the average team's productivity was far below where I believe it should be because of dull tools. Figure out where your company needs improvement the most and make it better.
If you have the leverage, 17 people in daily standups is a good problem to fix.
If I use tools that can give me reproducible builds, like Bazel or Nix, I won't need or want to use containers for development.
His point about protocol buffers (i.e. schema-out-of-band protocols) is unfortunately brief in this talk.
Depending on your use case, you may have to do a lot to work around protocol buffers not being self-describing. I haven't seen a good description of the problem online, but if you find yourself embedding JSON data in protobufs to avoid patching middleware services constantly, you should look at something like Avro or MessagePack or Amazon Ion.
I don't use evil-mode (anymore), but I still use Spacemacs. I'm too lazy to configure everything myself (language modes, Helm, Projectile, Magit, etc) so I use Spacemacs as a starting point and load a bunch of extra ELisp on top.
I'd recommend Spacemacs (even if you're not using evil) if you're new to Emacs and want to see how different and powerful a fully customized Emacs is when compared to the bare-bones experience of stock Emacs.
Can you go into detail on this?
Perhaps you would prefer something like Ion: https://amzn.github.io/ion-docs/guides/why.html