When was the last time you used Jenkins? I don't get the hate. Not only from you, but lots of people on the internet. What makes Jenkins stand out IMO is the community and the core maintainers, they are perhaps moving slow, but they are moving in the right directions. The interface looks really nice now, they've done a lot of ux improvements lately.
I haven't used Jenkins in a few years, so some of this might change, but in working with it I saw that Jenkins has a few fundamental flaws that I don't see them as working to change:
1. There is no central database to coordinate things. Rather it tries to manage serialization of important bits to/from XML for a lot of things, for a lot of concurrent processes. If you ever think you can manage concurrency better than MySQL/Postgres, you should examine your assumptions.
2. In part because of the dance-of-the-XMLs, when a lot of things are running at the same time Jenkins starts to come to a crawl, so you are limited on the number of worker nodes. At my last company that used Jenkins they instituted rules to keep below 100 worker nodes (and usually less than that) per Jenkins. This lead to fleets of Jenkins servers (and even a Jenkins server to build Jenkins servers as a service), and lots of wasted time for worker nodes.
3. "Everything is a plugin" sounds great, but it winds up with lots of plugins that don't necessarily work with each other, often in subtle ways. In the community this wound up with blessed sets of plugins that most people used, and then you gambled with a few others you felt you needed. Part of this problem is the choice of XMLs-as-database, but it goes farther than that.
4. The way the server/client protocol works is to ship serialized Java processes to the client, which then runs it, and reserializes the process to ship back at the end. This is rather than having something like RPC. This winds up being very fragile (e.g.: communications breaks were a constant problem), makes troubleshooting a pain, and prevents you from doing things like restarting the node in the middle of a job (so you usually have Jenkins work on a Launchpad, and have a separate device-under-test).
Some of these could be worked on, but there seemed to be no desire in the community to make the large changes that would be required. In fact there seemed to be pride in all of these decisions, as if they were bold ideas that somehow made things better.
both the old & new interfaces to Jenkins are riddled with bugs, work seems to be maintenance mode, across the plugin ecosystem too
If you are talking about Jenkins-X, that is a different story, it's basically a rewrite to Kubernetes. I haven't talked to anyone actually using it, if you go k8s, you are far more likely to go argo
This is just awesome! But seems like a closed source project, and the pricing page returns HTTP 404.
Are there any open source alternatives like this? First time I hear about this idea. However, I can imagine it wouldn't take much effort to implement the basics. Chromium even has a design mode you can activate by typing `document.designMode='on'` in the console. Then you would just need to write a little javascript that handles auth, a save button, and a backend to persist the altered html.
fwiw, for this kind of tech - personal level projects - there is not a snowball's first summer outing in hell's chance I'm going to pay for someone else to host my thing remotely. I would like to just self host, and if it was good I would buy a license for it so I can self host - but I think you have a customer in mind that doesn't exist.
Your ideal customer a) is extremely technically proficient, such that they are even capable of finding this in the first place, and their brain doesn't glaze over at "jQuery is Your Starting Point" - the opening line of your docs. b) They for some reason would rather pay for someone else to do the world's easiest hosting job and deal with whatever baggage and limitations come with this.
Or am I misunderstanding? Like it's a nodejs server on some aws box. Charging people for this is fine, but not allowing them to do it themselves seems... ridiculous?
You gotta eat, I know, but I'm wondering who it is that is ok paying for someone else to do the easiest part what they do for a living.
I think you're underestimating the market here. It's not just extremely technically proficient people, it's the glitch people, the "custom myspace theme" people, possibly even the jsfiddle people.
The `/save` endpoint looks almost trivial. Knocking up a mimic wouldn't take much. The client libs will be interesting, but from the looks of things they're not quite there yet.
Mavo seems pretty similar, saves to github, allows flipping the UI to admin/editor mode https://mavo.io/
I really liked this when it was launched and thought it had a great deal of potential when it launched. I think the main difference is that it's more focused on content-editing, not updating the code of the page itself.
Similar story happened to me once: I had recently got my drivers license, and one day went to bed early (completely sober). In my dream that night I got drunk, took my dads car and wrecked it. When I woke up next morning, first thing I did was to take dads car to pick up a friend of mine. I felt so hung over, and was driving like I was "still drunk". I had that feeling the whole day. Still remember it well today, even 20 years later.
One cool use case for this could be "generative hybrid video meetings"; when I participate in a teams meeting and the majority is in the same physical room, the video conference software could read the wall camera video feed and generate individual video streams of each person as if they sat just in front of me.
Of all things this must be the most boring use case for this crazy looking new technology. But hybrid video meetings have always annoyed me and I think to myself that surely there must be a better way (and why hasn't it arrived yet?).
Very interesting! Is there reason to believe that the outcome would be different if the experiment was re-run but replacing the humans with coin-flipping machines?
This is really stupid, old, legacy sh*t. If the USB HumanInoutDevice spec would support full unicode, keyboards could just send unicode directly and not rely on a not-known-by-the-keyboard-firmware language setting. The language settings would be implemented in the keyboard firmware, but with todays hardware shouldn't be a problem.
While I get the sentiment, implementing full Unicode support directly in the keyboard firmware would pose challenges. Consider mechanical keyboards where keys are swappable; you'd need a mechanism to inform the firmware of the current configuration, either through dip switches or a separate firmware tool. It's not as straightforward as it might seem.
That and also it wouldn't be able to express modifier key state, locks, etc, so it would have to coexist with the existing scancode-based input methods.
If you represent Unicode codepoints as unsigned 32-bit integers, you have the eleven high bits free for representing modifier keys. You can even represent changes of state for the modifier keys without a normal key press by sending the modifier bits with a NUL character.
Some standard for storing or otherwise representing the keyboard layout in hardware would be nice. Or at least some kind of identifier that says what kind of keyboard it is enough to build a table of the most common layouts.
Hell, while we're dreaming here, it'd be nice to have OS-level support for telling which devices keypresses come from so you can have a different layout on every connected keyboard or even turn extra keyboards into macro pads. (I've seen some setups like this, each with varying levels of jank.)
Right now any keyboard can use any layout transparently, minus the keycaps printing but fingers don't have eyes, so it doesn't really matter. Changing that is what would be really stupid.
Been using LazyVim for professional go development for over a year now. I can't see any features promised here that I do not already have. LazyVim is a NeoVim configuration for those who don't know. Together with the golsp its insane how good it is. Sometimes I miss those heavy refactoring functions that Jetbrains provide though, like extract function etc.
Absolutely agree. LunarVim is my NeoVim configuration of choice and 90% of my usual workflow is present and with the missing rest I can still manage to be productive enough.
I don't see not having LSP as a positive aspect to mention by their IDE.
I use NeoVim and write the configuration myself. It's great with LSPs and I love the fact that I can interface with my editor in Lua.
In the same way, I love how Blenders interface is entirely scriptable with python. I wish Digital Audio Workstations like Ableton Live offered something similar.
Ever since I learned how to use the Miryoku layout, I've been using vim with the hjkl navigation-keys shifted one position to the right. Those are also my arrow keys on a separate layer in the keyboard firmware. And I never looked back, this is how it really should be!
What kind of keyboard do you have or what are some favorite ones you have tried? Been looking at bastardkb.com a lot recently, but feel frozen with choice.
