• 0 Posts
  • 27 Comments
Joined 11 months ago
cake
Cake day: August 7th, 2023

help-circle








  • Why wait and hope for C++ to get where modern languages are now? I know there’s value in the shared experience in C++ that if adapted would make it stronger, but I can only see a development of C++ having to force a drop of a lot of outdated stuff to even get started on being more suitable.

    But the language is just not comfortable to me. From large amounts of anything creating undefined behavior, the god awful header files which I hate with a passion, tough error messages and such. I also met a fun collision of C++ in Visual Studio and using it with CMake in CLion.

    I’ve just started looking at rust for fun, and outside not understanding all the errors messages with the bounded stuff yet, figuring out what type of string I should use or pass, and the slow climb up the skill curve, it’s pretty nice. Installing stuff is as easy as copy pasting the name into the cargo file!

    Rust is just the prospective replacement of C++ though, people act like the White house said that C++ should be replaced by rust now. But the just recommend it and other languages, C# will do for a lot of people that does not need the performance and detail that the aforementioned languages target. Python is targeting a whole different use, but often combined with the faster ones.

    C++ will live a long time, and if the popularity dies down it will surely be very profitable to be a developer on the critical systems that use it many years from now. I just don’t think an evolution of C++ is going to bring what the world needs, particularly because of the large amount of existing memory related security vulnerabilities. If things were good as they are now, this recommendation would not be made to begin with.





  • Already been explained a few times, but GPU encoders are hardware with fixed options, with some leeway in presets and such. They are specialized to handle a set of profiles.

    They use methods which work well in the specialized hardware. They do not have the memory that a software encoder can use for example to comb through a large amount of frames, but they can specialize the encoding flow and hardware to the calculations. Hardware encoded can not do everything software encoders do, nor can they be as thorough because of constraints.

    Even the decoders are like that, for example my player will crash trying to hardware decode AV1 encoded with super resolution frames, frames that have a lower resolution that are supposed to be upscale by the decoder. (a feature in AV1, that hardware decoder profiles do not support, afaik.)




  • I do think the idea is pretty neat, although it’s pretty close to returning structured data like json.

    A slight disclaimer that these people are smarter than me, and know better about what we are talking about, so I may be wrong here on some assumptions. But I do get a bit of feeling they are trying to solve a trivial problem, at least in their use case. Ultimately there are only so many lecturers, and so many man lectures at a given time. The total data amount wouldn’t be so much, and you can easily group by and sort on client side to achieve the original table which is show on a per lecturer basis. A little redundancy is in my opinion preferred over a query that returns 3 tables that then needs additional complicated work. I also find arguments about overlapping names to not be something the database should be handling, it falls on the data owners/manager instead. Academia is a wild west at times, but either this table is presentation only or a link to lecturer or lecture. And in the latter case, you’ll already throw in the ids so they can be used in an URL to some other site.

    While this can have significant less bandwidth, it also risks falling as soon as more data is introduced, as you’re putting the large join operations on the client when you can get free optimizations from the SQL engine you use. I know not having duplicate data could be a thing for something where I work, where essentially we have hourly breakdowns but fetch at least the entire day for a single set of parameters. So that means 24x data for a surprisingly high amount of columns. When we only need 2 of them on the hourly level! But in this case, the data doesn’t strictly need many joins as it has a lot of the information itself, along with there being too much data to join on the client side anyways for this to feel ideal. I feel you’ll increase the complexity a bit too much as well. A big advantage of sql is how easy it is to understand what you are getting.

    Its somewhat of a solved problem, if the performance becomes a problem, since we can return nested data anyways. So we can already today technically return a row where the hour(I think, never tried a date before) and value columns have arrays instead of a single value. We just haven’t done it because it is not a big enough problem yet.




  • I think the key fault lies in that most companies are publicly traded stock companies.

    It challenges what corporations are at the heart. A company owned through stocks is controlled by those stock holders, and exist to make the stock holders money. It’s expected for the stock to be worth it by growing, not paying out dividends. (but that is also another layer)

    But that’s not why a company should exist, it should turn a profit but ultimately it’s about being a source of income to its workers. But stocks go against that, since stocks seek to extract money to the non-working owners. Well paid workers is rather contrary to the goal of the stock owners, as long as you can keep going.

    The advantage of stock companies were getting investment to start and grow, but it forever shackles the company bar some rich maniac buys the whole thing for his own crazed ideas.

    Private companies aren’t guaranteed to be good either, but if they are set up right they at least aren’t just a funnel of money for the people at the top.

    Its because so much money can be gotten out of the perpetual invest, grow, squeeze and sell that things are as they are today. You’re not a worthy company if you just increase your cash flow in line with inflation.

    The need to grow also comes back as enshitification, planned obsolescence (or just made as cheap as possible), high focus on consumable products or subscriptions to ensure a steady flow of income. Making a product lasting for life? One and done, you’ll grow until the market is saturated and then collapse because the cash flow simply won’t be there.

    Its especially noticeable when the economy takes a hit, all things go from being good investment objects to being something that needs to turn profit. So all the future profit is dropped, tons of layoffs, and rapidly increasing subscription costs. All to counter the reduced demand. Take streaming, the market fragmented, interest rates spiked so holding debt is bad, consumers have less money to spend easily. So the big ones take steps, more ads, crack down on sharing, layoffs, reduced selection and cancelation of various shows and projects. And then stock holders can be happy they once again have a good year and good growth of profit despite turbulent times.

    Edit: By contrast a private company is not beholden to any requirement to cancerous growth. It too will be hurt by not having steady cash flow, but they don’t need to grow until they are so big that they need constant growth to stay alive. But a private company can be steady for years without problem.


  • Brushing off safety in a single small paragraph sure makes me feel like its not trying to make a serious argument. Sure a handyman likes the simplicity and freedom, but considering this:

    In 2019, a Microsoft security engineer reported that 70% of all security vulnerabilities were caused by memory safety issues.[7]

    From Wikipedia, it’s pretty clear memory security is a pretty substantial topic in the programming world. Brushing that off because you do not care makes for a bad argument.