91–100 of 152 posts
Maybe they don't want to refocus away from the public, but it could work.
So I see a lot of confusion about what LWN is on here. While it provides a detailed write up of recent kernel development for sure, it is far from the only thing they do. LWN is first and foremost a great way to stay on top of the most important developments in the free/open-source community, without having to browse tens of mailing list discussions on a weekly basis. I see it as giving me a way to keep a tap on the…
And many of the actual kernel devs, and other important and notable FOSS coders, as regulars in the comments. "LWN: A site you want to read the comments on."
I've never been a subscriber of this page and I don't think I am their real target audience. But I'm a professional programmer and I have been using Linux for around 15 years. I must say that this website comes across as very unprofessional due to the total lack of any design elements which would make it more easy to consume the content (spacing, choice of font). Also it seems like they don't use CSS to enhance the s…
LWN gets me what I want. It is the most important resource for a linux kernel or in general Free Software enthusiast. Average HN crowd perhaps does not fit into that stereotype.
Earlier quoted context omitted.
> I must say that this website comes across as very unprofessional due to the total lack of any design elements which would make it more easy to consume the content (spacing, choice of font). Say what? On the contrary, I think that it's splendidly simple to read LWN, because there's no distraction. It's a good, clean site; it respects the styling I instruct my browser to apply to it; it displays just fine in links, l…
As a reader of a website, I usually primarily care about what the page looks like when it's rendered, as opposed to how clean the HTML is. Granted, the current trend to make everything feel like a shitty JavaScript application would be taking it too far, but lwn.net is definitely not a pleasure to read. Yes, it displays "just fine" in links, lynx, elinks, etc., if your definition of "just fine" is Fefe's Blog.
Hey, fefe has some pretty nice stylesheets for his blog
https://blog.fefe.de/?css=darkgreen.css
https://blog.fefe.de/?css=cold_blue.css
https://blog.fefe.de/?css=ascii.css
https://blog.fefe.de/?css=topaz.css
https://blog.fefe.de/?css=janvsfefe.css
There is no "Subscribe" link anywhere in the text of this article or on the web page that hosts it ( http://lwn.net/Articles/696017/ ). I was able to find the link from the front page, but it's kind of hidden -- https://lwn.net/subscribe/Info which says "Get started! The first step is to log into LWN. If you do not yet have an account, please create one now; otherwise, please log in to continue:". Which seems like a…
Okay found it in the middle of a paragraph on the front page. I think the nav could be improved.
At a couple of places I have worked at we had a group subscription for the department, $45 it not terribly hard to get approved. I think its a great perk to list for prospective candidates too.
Earlier quoted context omitted.
> this website comes across as very unprofessional due to the total lack of any design elements Really? I've always viewed plain HTML sites in the complete opposite way. They tend to have really good, well thought-out content. There's no filler or clickbait with them.
I think this (humorous) site is relevant, here: http://bettermotherfuckingwebsite.com/ Excessive CSS is, well, excessive. That said, a tiny pinch of CSS goes a long way towards making a page readable and aesthetic.
Most people here are commenting about the look and feel of LWN, I really don't have any complaints about the UI/UX so far, I don't expect to read LWN on my mobile phone. I think the main reason of the drop in readership is firstly kernel development is very involved and detailed, LWN mostly reflects the kernel mailing list and associated events and tech talks. I guess what I find most difficult as an outsider of the…
If the kernel has anything like an epic, there is multiple concurrent epics because the Linux is not a monolithic project. Nor are epics related to any kernel version.
For example, each major GPU driver (radeon, novaeu, intel) manages their own development, and push things upstream. DRM (the kernel part of DRI) interacts with those guys, and DRM pushes things upstream.
Network drivers and the network core are managed by small teams, push things to each other (such as adding support for major intrusive features like, say, when they added segment offload support, or recently genericfied the interface for that to support more protocols; or alternatively, when they started making more complex DMA patterns like scatter-gather and other zero-copy methodologies happen). The network guys push things to each other, and push things upstream.
The storage guys also do that, storage drivers and storage core push things to each other, and push things upstream.
Every possible major section of the kernel is a project in of itself, and have project leaders, and have parts that are ran by different people.
Generally, you don't push a patch to lkml by itself, and then you're done; this almost never happens. What happens more often is you go to one of the people who manage that part of the kernel, or has significant experience with that part of the kernel, and discuss your patch with them, and then they will try to help you make a patch that can be merged upstream.
More patches are rejected than committed because of how this works. Linus, or any other kernel maintainer, does not want your patch if it hasn't been ok'ed by the people who maintain those other parts of the kernel unless it is a small patch that does something obviously useful.
And what about the companies that just push drivers? Companies employ kernel hackers that know how to write drivers. For example, Intel employs the Intel GPU driver guys, Radeon employs the Radeon GPU guys, and all those guys are already major authors in the X/DRI/Gallium/DRM/whatever community; the infrastructure to make that all work is shaped by the hardware, the hardware is not shaped by the infrastructure.
Earlier quoted context omitted.
I think this (humorous) site is relevant, here: http://bettermotherfuckingwebsite.com/ Excessive CSS is, well, excessive. That said, a tiny pinch of CSS goes a long way towards making a page readable and aesthetic.
I liken CSS and JS to salt: putting a little on makes things better. But pouring a lot on quickly makes things worse. Scarcity is the key