[-] schalkneethling@programming.dev 3 points 7 months ago

Amen to that :) We have to start somewhere though, right :)

11
7
[-] schalkneethling@programming.dev 1 points 7 months ago

Thank you for the great feedback! This is one of the benefits of undertaking a project such as this in the open. I hear you with the <base> element. I was in two minds whether I should even include it. I am thinking now that I should, but introduce it merely for completeness and recommend not using it. I wonder if it will ever be deprecated.

[-] schalkneethling@programming.dev 1 points 7 months ago

Thank you for the feedback. I am also reading through the spec as a core part of writing the book. It is indeed critical to do so.

20

Today I am super proud to announce that I have finally picked up the task of finishing my book titled, "HTML: A Comprehensive Guide". I am writing the book in public and releasing it under the MIT license.

13
13
[-] schalkneethling@programming.dev 1 points 7 months ago

Aaaah, gotcha. I have to say, that article is not my proudest moment and also not entirely my idea 😉

[-] schalkneethling@programming.dev 1 points 7 months ago

Many open source projects will require licenses when you use it in a commercial environment.

I would argue that that is not an open source project then.

[-] schalkneethling@programming.dev 1 points 7 months ago

This is very interesting. I agree that some of the formatting puzzled me as well. I would assume this follows some standard even when the use of said standard is uncommon. I have for example not seen 1.000,00 € used, but I thought that perhaps if you live in Germany, France, or another EU country then it is common.

11
1
12
7
8
7
15
[-] schalkneethling@programming.dev 4 points 10 months ago

I hear you, but I also do not agree entirely. For me it is two-fold.

  1. If you intend to try and use open source as a sales vehicle or a pure marketing tool, then use the appropriate license from the start i.e. be transparent and honest.

  2. If open source and community are truly at the heart of your organization, adopt a license that makes this clear like the Apache License, and focus on adding value through services built on top or in service of the open source piece. Also, in this scenario, you must support both the community and the open source project(s) itself not just your customers. If this is not what you have in mind, see point 1 above.

For some reason, a bunch of people in the opensource community are hanging on to ideals and clutching their pearls when faced with reality: you live in a capitalist, dog-eat-dog world where people do not share the same ideals and will happily exploit others with no qualms whatsoever

True, but again, if we want this to change and/or find a balance, we need people and organizations who actively push back and clutch their pearls as you stated. If we lie down and simply accept the status quo, it will never change and those at the top will always be dictating the terms down to everyone else.

[-] schalkneethling@programming.dev 2 points 10 months ago

Care to expand on those mixed feelings?

[-] schalkneethling@programming.dev 2 points 10 months ago

Mine is a Macbook Pro 2013 with a Broadcom wireless device.

[-] schalkneethling@programming.dev 3 points 11 months ago

I do not have much, if anything to add, other than saying, "What @silas@programming.dev said." - Great advice.

view more: next ›

schalkneethling

joined 1 year ago