Language Selection

English French German Italian Portuguese Spanish

Tux Machine's editorial picks are...

Good as they are
54% (74 votes)
Need improving
9% (13 votes)
Too many
6% (8 votes)
Too few
3% (4 votes)
Need commentary
28% (38 votes)
Total votes: 137

too many links

Take a look at this for example. http://i.imgur.com/MQ21f8r.png way too many links and it actually keeps going if I scroll down.
No one is going to read all of that. People should be easily able to recognise new content on the website.

Front page

Is shortened summaries, especially of such posts, were to appear in the front page, would that be an improvement? It would necessitate more clicking (to expand the post) but it would save space.

front page

Yes definitely Smile The short summary can include small headlines "New releases from so and so' and "Learn new tricks to fix this and tips to do that" or "New howtos for...." or "Guides for compiling this and that and migrating from software A to B etc.." then when the readers click 'read more', they see the full set of links.

And again, thank you for your dedication towards making the website more user friendly Smile

Shortening

I will be shortening long posts with many links from now on.

the leftovers

the leftovers thing with many links is way too annoying in my opinion.

Suggestion

Do you suggest that they don't get posted at all or just not in this current form?

Not in it's current form.

Not in it's current form. Perhaps make a separate page for "tutorials", or left overs. call it something like 'back news' or short news. And then keep the major articles on the front page Smile

(and thank you for replying)

Feeds

The problem is, how will people subscribe to those pages or be made aware of their existence? it would basically fragment the flow, wouldn't it? Some sites like FAIR.org do this (splitting to sections) and it complicates syndication.

More in Tux Machines

GNU Compiler and Bison 3.2.2 Release

  • Intel Cascade Lake Support Posted For The GCC Compiler
    Intel developers have submitted their GCC compiler enablement patch for the Cascade Lake 14nm CPUs due out starting in early 2019. The GNU Compiler Collection patch adds support for the -march=cascadelake target for generating optimized code for these upcoming server and enthusiast class processors.
  • Bison 3.2.2 released [stable]
    Bison 3.2 brought massive improvements to the deterministic C++ skeleton, lalr1.cc. When variants are enabled and the compiler supports C++11 or better, move-only types can now be used for semantic values. C++98 support is not deprecated. Please see the NEWS below for more details. Many thanks to Frank Heckenbach for paving the way for this release with his implementation of a skeleton in C++17, and to Nelson H. F. Beebe for testing exhaustively portability issues.

Industrial dev board builds on Raspberry Pi CM3

Kontron announced an industrial-focused “Passepartout” development kit built around a Raspberry Pi Compute Module 3 Light and equipped with a dual Ethernet, HDMI, CAN, 1-Wire, RPi 40-pin connectors. Kontron announced its first Raspberry Pi based product. The Passepartout — which is French for “goes everywhere” and the name of Phileas Fogg’s valet in Jules Verne’s “Around the World in Eighty Days” — builds upon the Linux-driven Raspberry Pi Compute Module 3 Light (CM3L). The Light version lacks the 4GB of eMMC flash of the standard CM3 module but still supports eMMC or microSD storage. The CM3L is otherwise identical, with features including a quad-core, 1.2GHz Broadcom BCM2837 and 1GB of LPDDR2 RAM. Read more

Patches For The Better Spectre STIBP Approach Revised - Version 7 Under Review

Version 7 of the task property based options to enable Spectre V2 userspace-userspace protection patches, a.k.a. the work offering improved / less regressing approach for STIBP, is now available for testing and code review. Tim Chen of Intel sent out the seventh revision to these patches on Tuesday night. Besides the Spectre V2 app-to-app protection modes, these patches include the work for disabling STIBP (Single Thread Indirect Branch Predictors) when enhanced IBRS (Indirect Branch Restricted Speculation) is supported/used, and allowing for STIBP to be enabled manually and just by default for non-dumpable tasks. Read more

today's howtos