• 0 Posts
  • 17 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle

  • Adding more light rail wherever it makes sense is definitely a good plan (and should happen), but improving bus networks gives a lot more bang for the buck than focusing only on light rail. Features like off-board fare collection (paying at the bus stop, not on the vehicle), bus signal priority (extending greens and shortening reds as buses approach traffic lights), and dedicated bus lanes all improve the overall speed of buses and therefore the overall rider experience. Expanding the prevalence of these features should be a priority everywhere, particularly on higher-ridership routes.


  • Unfortunately the software industry (at least in the US) has applied the term “engineer” basically across the board to software developers instead of only for properly trained and licensed engineers as in other fields (civil engineering, mechanical engineering, etc). Part of this is due to a lack of a formal software engineering licensing system, but the desire for fancy titles is certainly something that played a role in this.

    My understanding is that other countries, like Canada, do have strict requirements for the use of the term “engineer”, but unfortunately that ship appears to have sailed in the US due to inertia and the intransigence of Silicon Valley-type companies.











  • I’m hoping that, someday, we have support for what I described in another post:

    It would be very beneficial to have clients that support aggregating equivalent communities from multiple instances. When viewing a post from the aggregated community there could be a section at the top saying “Viewing comments from:” and then a dropdown to choose between “all instances”, “lemmy.world”, “lemmy.ml”, etc. When viewing all comments, they would be in one combined feed, without the user needing to care about which underlying post holds the specific thread they’re looking at.

    Similarly, when users post something to an aggregate community, they could select whether it’s posted to all the included communities, only one, or some specific subset.


  • It would be very beneficial to have clients that support aggregating equivalent communities from multiple instances. When viewing a post from the aggregated community there could be a section at the top saying “Viewing comments from:” and then a dropdown to choose between “all instances”, “lemmy.world”, “lemmy.ml”, etc. When viewing all comments, they would be in one combined feed, without the user needing to care about which underlying post holds the specific thread they’re looking at.

    Similarly, when users post something to an aggregate community, they could select whether it’s posted to all the included communities, only one, or some specific subset.