The real deal y0

  • 1 Post
  • 93 Comments
Joined 1 year ago
cake
Cake day: July 16th, 2023

help-circle

  • Thanks for the response. Ive heard of rust’s compiler being very smart and checking a ton of stuff. Its good thing it does, but i feel like there are things that can cause this issues rust cant catch. Cant put my finger on it.
    What would rust do if you have a class A create something on the heap, and it passes this variable ( by ref ? ) to class B, which saves the value into a private variable in class B. Class A gets out of scope, and would be cleaned up. What it put on the heap would be cleaned up, but class B still has a reference(?) to the value on the heap, no? How would rust handle such a case?





  • Yes!
    They have released multiple new mainboards for the framework 13 which upgraded the cpu. This is a new mainboard with the latest intel cpus. They have always allowed everyone to just buy the board so they can upgrade their existing framework 13’s, thats their whole stick : modularity.
    This time they also have a new screen panel and battery you could get to upgrade your system.

    Also obviously new systems can be bought with the new hardware from the get go too.

    I have a framework 16 that my boss got for me. Im a trial to see if we can save money by going framework instead of dell for the laptops developers use as things like the ports on the side, batteries and mainboards are easily replaced and upgraded. No need to waste +2600 euro every 3 years per laptop either if we can just swap the mainboard. They didnt want to finance the gpu, but when the laptop is mine after 3 years i will probably get the gpu for it :)
    (In a framework 16 a gpu can be plugged in or replaced. Framework 13’s always use integrated gpu )






  • Ye, the sm64 was just a jit emulation, you are correct there. Not gonna deny that either. The sms and smg emulations are interesting and impressive though. They basically use a combination of jit compilation and aot compilation to basically take in the rom and adjust code as they go, but its technically running +/- natively, if i read the switchbrew wiki page correctly, thanks to the aot compilation. I find that impressive, from a technical standpoint.
    Could they have added more and do more changes? Yes, ofcourse. Im not saying the fan made stuff isnt impressive, it is and i love it!
    But for nintendo, who strives to create new experiences and things, not rehashing older stuff, is why they kept it basic. For them adding that stuff doesnt make sense as the game doesnt add new enough experiences. They dont care if a bug is fixed or graphics are improved. Those dont get you new experiences or gameplay mechanics. Thats what nintendo strives for.

    Again, if that is a good stance to have as a company i leave up to others to make opinions on, thats not up to me to decide or voice my opinion on ^^

    Fyi, since you seem to know what youre talking about, nintendo’s r&d have used open source projects before internally and we assume it is done to look at older games and see how they worked or if they could be used to make projects like sm3d ( without doing what the license doesnt permit )



  • Has nothing to do with their closed eco system. They basically did similar stuff with some of the stuff in the sm3d collection thingy.
    Nintendo is a company that only wants make new stuff, innovations.
    For example, they ( mostly miyomoto ) has been quoted to not understand that people want another f-zero, as the game’s principals and ideas have been fully flushed out and no new ideas could make it feel like something new.
    They also usually dont do remakes/remasters unless its so new/different it can be considered a new game ( see metroid 2 on 3ds ).

    If that is a smart business position to have, i will leave for you to decide, but do get your facts a bit straight :)

    EDIT: also, nintendo has used open source projects for internal projects before, so idk how “closed ecosystem” is part of their stuff :)





  • In principal, the change is good for reasons you mentioned. However microsoft has :

    • bypassed any default screens in the past, allowing edge to be set default without user input.
    • has added very annoying screens when changing default applications asking the user multiple times if they are sure.
    • has added special protocols for applications and set edge as default browser to bypass default application settings in all office applications ( outlook, teams, word, … ).

    They just can not be trusted with this, they have proven this in the past…


  • The problem with java is the language and how it works itself, and not the byte code idea.
    I say that as a few things do that and .net, java and wasm are the first that jump to mind.
    Hell, pure technically any programming language that is not asm does that :')

    My problem is java itself, not its byte code. Wasm as advantage, imo, is that its not stuck to a single language like java is. .net blazor can build to wasm, but you could also use c++ to compile wasm applications :)