So on the surface it seems that we already had many of these types of orgs, but they killed them all and spun up their own renamed and rebadged versions.
That being said, this project does seem like a potential big win.
I've always had stuff like this turned down by Netbox, they argue they want to model the logical topology as a source to trust, not the physicality, but then they model rack U placement. I'm always puzzled by their stance.
Like you can't model 1 cat5 split into two 100mb terminations, patch panels are kinda of hack, I think you can now but forever you couldn't just swap a termination direction because logically why would you (but their UI gets messy when 44 are done A-B and the 45th B-A)
Anyway that's thoughts as of maybe v2 or 3? Before the new UI when it was all jquery.
Netbox project used to go on and on about the philosophical justifications for not including n-type connections or different types of LMR. But the most recent release notes that I read had a blurb about all the new coax cable types they are supporting. I understand having limited time but instead of saying "no" they always had to make lofty philosophical arguments. It's weird.
One of the achievements in my career I’m lowkey proudest of is sneaking in the rewire of about 45,000 ports on a campus that were split pair after an explicit project to do so was shot down.
Of course, but a splitter in a PON network or a WDM device are perhaps better examples of things that are hacky to model. Multi-fibre cables and splices are another. Netbox is great for some simple applications, and it's fantastic OSS, but in practice falls short for many use cases.
Yeh it's awful, but all of our CCTV was wired like this through patch panels with 24v/48v power injectors. 2 cameras a cable. So that's what I needed to document, because in reality I can't book scaffolding and change rooftop cameras for a documentation tool.
Oh I wasn't aware of this actually being an intended usecase. And yes like the other poster said, pairing it with a phone infrastructure was more common (in the days before these went all IP of course).
It was a bit of my OCD being triggered as well. I love neat cabling at work (at home it is chaos funnily enough).
Netbox is full of these kinds of things. Where people ask for stuff or even create PRs for it and the Maintainer of Netbox shoots it down because reason.
Wow, that second one was just straight up mean spirited. Doesn't feel like the responder even read it, given the comment about needing a discussion at the end despite it being linked. Not even mentioning the frankly unrealistic expectations of quality is annoying when the contribution guide didn't have those kinds of insane requirements then and still doesn't now.
I'll believe it when I see it wishing them the best!
> To streamline development and shorten time-to-market, VSORA embraces industry standards: our toolchain is built on LLVM and supports common frameworks like ONNX and PyTorch, minimizing integration effort and customer cost.
I think there's just an instinctual draw to building a new browser, partly because so much of our modern software is dependent on web apps. Not sure if SerenityOS has been progressing as much as it originally did now that Andreas is all enamored with Ladybird.
Many have brought up more websockets instead of REST API calls. It looks like they're already working in that direction.. scroll down to "Developer tools and APIs": https://nextcloud.com/blog/nextcloud-hub25-autumn/
This post completely misses the point. Linear downloads ~6.1mb of JS over the network, decompressed to ~31mb and still feels snappy.
Applications like linear and nextcloud aren't designed to be opened and closed constantly. You open them once and then work in that tab for the remainder of your session.
As others have pointed out in this thread, "feeling slow" is mostly due to the number of fetch requests and the backend serving those requests.
Anyone have any new suggestions for similar apps on the Android side of things?
I know the full-blown Linux terminal is "released", but only for Pixel phones by what I've been able to find. Definitely can't install it on my OnePlus 13 yet.
I've been using JuiceSSH for years, but it's getting a bit long in the tooth and doesn't receive updates for years anymore either.
US Digital Service (USDS) was also "renamed" and turned into DOGE (https://en.wikipedia.org/wiki/United_States_Digital_Service).
So on the surface it seems that we already had many of these types of orgs, but they killed them all and spun up their own renamed and rebadged versions.
That being said, this project does seem like a potential big win.
reply