ikeepforgetting

vor 13 Jahrendiscuss

Listening to the same port requires processes with the same uid.

ikeepforgetting

vor 13 Jahrendiscuss

The only reason they backed off of it was because of the bad press it gave them in the first place.

ikeepforgetting

vor 13 Jahrendiscuss

Somebody finally found a use for them!

ikeepforgetting

vor 13 Jahrendiscuss

Well, they're always slower than not having them. Having a few layers on top of each other starts to add up. It's very easy to lose track of the bottlenecks of 2 or more layers below the one you're working in. There is a reason HTTP.sys runs in kernel space and BSD sockets don't. And there's a reason both of them are slower than XMLHttpRequests.

PS. The fact that you can point to one (or a few) efficient abstractions doesn't mean they all are.

ikeepforgetting

vor 13 Jahrendiscuss

I work in an area that requires a lot of high performance computing and there is a reason people in this area like code simplicity. Stacking layer upon layer of complex algorithms is a lot more difficult to reason about than having a simple and elegant system that's close to the metal.

There is a recent trend of building more and more complex systems, have less coupling and 'good oop'. That's all good and nice but simple code is:

  - more maintainable (a complex nest of objects & function calls all loosely coupled isn't)
  - a lot more readable
  - easier to optimize
  - better for your sanity

Some languages have build a culture of extreme complexity and are notable for building huge structures and systems to do simple tasks. Having a 50K lines of code dedicated to just inversion of control or O/R mapping makes a problem a lot more complex than it probably needs to be.

ikeepforgetting

vor 13 Jahrendiscuss

My guess is that removing 2-5 layers of abstraction can get you pretty far along.

comments