gravitas_deficiency

joined 1 year ago
[–] gravitas_deficiency@sh.itjust.works 2 points 19 hours ago (1 children)

Fair points.

I’d say they could make three versions:

  • a “clean” single-port WiFi-only model but with actually good WiFi hardware (so, 7 if possible; 6e at least)
  • the current model, but with 2x2.5
  • one with no WiFi and at least 4 ports, including at least 2x2.5
[–] gravitas_deficiency@sh.itjust.works 19 points 21 hours ago (1 children)

What they could have done is to try to reverse the hollowing out of their engineering divisions, and give them more agency and control in leadership. Finance types trying to min/max the P/E ratio is what got them where they are. Serious tech companies that do REAL engineering can’t really follow the norms that Wall Street loves these days and expect to remain technically cutting-edge.

Engineers are not really plug-and-play. Institutional expertise is a real and meaningful thing. They got here because their leadership has ignored those facts for at least a couple decades now.

[–] gravitas_deficiency@sh.itjust.works 1 points 21 hours ago (3 children)

What’s wrong with having a switch? And why build in capability that people aren’t necessarily gonna use?

The intent of this is to be a cheap but capable homelab router. Building in more ports / integrating a managed or unmanaged switch / adding PoE is only going to drive up cost. BYO is absolutely the answer to “I want more ports” here.

Literally the ONLY thing they would need to do to make this perfect is to make the LAN port upgradable to 2.5G - anything past that and people are probably going to be looking at more serious enterprise-grade hardware anyways.

[–] gravitas_deficiency@sh.itjust.works 8 points 23 hours ago (1 children)

Flatpak has its issues, sure, but it’s better and more open than snap, while maintaining utterly simple usability.

[–] gravitas_deficiency@sh.itjust.works 37 points 1 day ago* (last edited 1 day ago) (3 children)

Tbh it’s not 100% his fault the engineering competence began to visibly crumble under his leadership, but at the same time he absolutely stayed the course that his predecessors chose, which is what got them here in the first place. So yeah, he deserves to be excoriated for this stuff, but so do his predecessors.

I mean either way you’re gonna bottleneck on the 1G port

[–] gravitas_deficiency@sh.itjust.works 16 points 1 day ago (6 children)

Uh, if you’re wanting to go above 1G, this thing is not going to cut the mustard. Seriously, why would they give it a 2.5G WAN port paired with a 1G LAN port? That’s so dumb.

[–] gravitas_deficiency@sh.itjust.works 23 points 1 day ago (5 children)

This would be potential impulse buy territory if it was 2x2.5… but a mix of 1 and 2.5 is frankly a tad baffling

GSV, and thank you very much for noticing

[–] gravitas_deficiency@sh.itjust.works 4 points 3 days ago (2 children)

Nothing, they’re just being an ass. Don’t worry about it.

You’re 100% right. And I have absolutely done this in the past when some dipshit has the bright idea to tie comp adjustments to SLOC metrics. And it’s more than just comments: you just make EVERYTHING a variable, duplicate as much as possible, and avoid terse syntax at all costs. It makes the codebase nigh unmaintainable… but hey, if you’re gonna hit me in the wallet if I don’t do that, I don’t fucking care about the quality of the codebase under those constraints.

view more: next ›