soenkeliebau

I think we are heading towards a bit of a shift in this regard. With the CRA in Europe and similar legislation in the States it will become more important to have "enterprise" services surrounding open source software. This is for example support, but also vulnerability assessment and similar things.

I may be mistaken here, but I think we will see pure functionality become less important to enterprise customers, which might (maybe not, but one can hope) proper open source business models more viable again.

same here, Germany

Aren't most responses not addressing the point of that study? I understand the abstract to say that the likelyhood of heart conditions due to contracting Covid is higher than due to vaccination?

That sounds interesting, I'd love to have a closer look at that, or get a demo, whatever you can currently offer :)

Thanks! That last one is probably the most important one as that mostly makes my comments "disappear" I think.. Regarding discussions on Slack, since our product is open source we would ideally like to keep discussions somewhere viewable and related to the code changes so that people can see what was discussed later on. It is a bit hard to find that on Slack, or do you have some form of "system" for tagging discussions in there?

Arguably selling support/services to a company using that product would help pay for developers that work on the product, which to me sounds like a benefit.

With the AGPL that would require dual licensing, and that draws flak as well.

I think the notion that OSS means there cannot be any money involved simply cannot hold true anymore these days. Software has become extremely complex and requires dedicated developers working on it - and they need to eat.

We are currently seeing a lot of companies changing their licensing model for a reason - because there is not currently a middle ground between OSS and a working business modell that the OSS crowd doesn't hate.

That being said, I'd love to be proven wrong here!

My personal opinion (and it is really just that - I cannot prove anything I say here) is that for a lot of those companies it is actually the risk of not being able to tell exactly what the AGPL would affect that is the main factor.

As I said, I'm explicitly not mentioning any alternative here because they all have issues, but the AGPL's wording is much more complicated than most and that (perceived) insecurity around it is my main criticism.

>Yes; if you're going to do this, then using AGPL is so much better than flavor-of-the-week license.

I'm not sure I agree. Yes, standardization is a good thing and AGPL is the "known evil", but having read it I do think that it is a very very complex piece of text - personally I'd go so far as to say that it is close to incomprehensible and would prefer pretty much anything else.

But even aside from that the sheer number of companies that point blank ban AGPL licensed software from being used in their stack could be used as an indicator as well. Though this may be due to the common misunderstanding that it is a viral license, which just goes back to my prior point on it not being clearly worded.

I won't even mention alternatives, I'm sure they all have issues, it is a complex topic, but if it were up to me the AGPL would not be my first license choice.

I'm not sure if I like your comparison to be honest.. not only is it not _just_ maintenance and filling the tank, if we stick with your picture, there is also things like buying the car, paying for it when no one uses it, insuring the car, repairing the car, general logistics of moving it around when someone has a one way rental, etc. - basically making it convenient for consumers to rent a car.

Looking at what "as a service" providers of open source software do though, that is taking it a step further, since they wrap the software in a layer that _smoothes_ out changes for the user. Going back to the rental company that would equate to the car manufacturer deciding the indicator needs to be on the right side of the steering wheel now and the rental company installing an adaptor so that it remains on the left for you, to keep the look and feel for the user the same.

Not a perfect comparison, but they never are :)

I don't know, in the EGA version the sarcophagus is much more prominent, which takes away the focus from the face quite a bit. To me the VGA version actually feels like it is more focussed on the face and shield by making the background less intrusive..

I think Kubernetes in principle gets a lot of things very right - but it has over time grown into this huge amorphous blob of complexity that makes it very easy to shoot yourself in the foot with, as many people said :)

That issue is not endemic to Kubernetes, but rather to any larger system past a certain age, you learn stuff as you go along and would do stuff differently if you did it again today - but you can't easily, because you cannot break compatibility for everybody using your stuff.

As a concrete example from the Kubernetes world, there is a talk by Tim Hockin [1] about how today, they would fundamentally design the api-server differently and base pretty much everything on CRDs.

[1] https://www.youtube.com/watch?v=ji0FWzFwNhA

This article made me feel really, really old!

It does have search, but I'd be willing to wager that the normal workflow when using that is "try searching for something, look at the results page, swear, clone, ..."

This, so much this!

Totally leaving aside the entire topic of that post, the comments could be used as a textbook case of a toxic "discussion" ... That in itself I think tells more about the state of things around wayland than everything else.

I look forward to seeing people try to step on other peoples heels on the street :)

For a querty or qwerz layout that would indeed work, if you moved one symbol key (- for german layout, ? for american). However in my keyboard loayout there actually is a letter in that place (j) [1]. And while I'm willing to compromise on modifiers, page up/down and the like, I draw a line at the stuff that I spent a lot of effort on learning to touch-type :)

As for using a navigation layer - perfectly happy with that 90% of the time, I already use that today, but for some things I just prefer actual cursor keys. For example selecting an entire word in an editor, you press shift to select, ctrl to jump a whole word and cursor for the direction to jump in. If you add a modifier to that, you start breaking fingers ..

[1] https://configure.ergodox-ez.com/moonlander/layouts/60ynN/la...

It's actually not as bad as it looks :)

I mostly learned the layout to reduce stress on my hands due to the more ergonomic placement of each letter.

From all the other layers I only use the cursor keys and L3 for []{}<>() and stuff like that, which are much easier to reach and I use a lot when programming.

I've looked at a few Moonlander setups for the keyboard layout that I use on their site [1][2][3] and to my mind the right half is simply missing one column of keys to get a proper cursor key block. Even the lying-L option ─┘ would mean missing the right shift key (which of course should probably be on the thumb block) and getting used to something different.

I'm not saying it wouldn't work, but for me being from Germany the keyboard is even more expensive than it is anyway and I'm not sure I'm willing to pay that much for the hope that I can adjust to it.

[1] https://configure.ergodox-ez.com/moonlander/layouts/mzD9d/la...

[2] https://configure.ergodox-ez.com/moonlander/layouts/60ynN/la...

[3] https://configure.ergodox-ez.com/moonlander/layouts/jXjMx/la...

I have looked at that keyboard a lot and am really tempted to splurge, but .. What is putting me of is the missing dedicated cursor keys at the bottom right. I use a layout on my current keyboard that has cursor keys on e,s,d,f with a modifier and use that a lot, but not exclusively.. I have the same issue with the ultimate hacking keyboard and others.

Has that bothered you at all, or did you find a layout that works for you and keeps the cursor keys?

Personally I think a mouse is not replaceable by anything else that even gives remotely the same productivity. What can be improved is how often you have to reach for your mouse and how much your hands have to move on the keyboard.

I have personally switched to a tiling window manager that allows me to do much with the keyboard, added the surfingkeys plugin to chrome to allow the same when browsing and switched to using the neo2 keyboard layout (this is for Germans, Dvorak or something similar might be better for you).

The combination of these factors has massively improved how much I need to reach for the mouse throughout the day.

But do they really, in all cases?

Due to the market share of AWS for many potential customers it will come down to a decision between

a) click here in the aws marketplace and have my service added to the invoice my company gets every month anyway

b) start the painful process of onboarding a new vendor, get a quote, have procurement haggle with them for months etc etc etc. (overstating it a bit, I know)

And that is where to me it becomes a question of using/abusing your position in the market to a certain extent..

Without wanting to come down on either side of the argument I'd like to say that the Pull Requests they reference in the blog post are over a span of roughly two years and touched somewhere in the vicinity of 1k lines of code. One of them changed one line by adding a synchronized modifier to a function..

I'd not consider that actively developing a product and adding new features.