Új hozzászólás Aktív témák

• #61833 S_x96x_S addikt PuMbA #61825

  Új Válasz 2023-07-12 16:19:31 #61833

  Új hozzászólás

  Összes hozzászólása itt Válaszok az összes hozzászólására itt Válaszok erre a hozzászólásra

  Privát üzenet küldése

  

  S_x96x_S

  addikt

  válasz PuMbA #61825 üzenetére

  > Pont ezért fizetsz a zárt forráskódért. Szólsz és javítják.

  <Ironia ON>
  és ez szerencsére ez minden játéknál és programnál így is van,
  és emiatt nincsenek már bugok a játékokban, vagy hamar megjavulnak
  ...
  <Ironia OFF>

  amúgy a gyakorlatban minden szoftver licensz tele van felelősség áthárítással ..
  és sokszor a "reverse enginering" is jogilag szürke terület ..
  szóval szívás a köbön ...

  Microsoft Win 11 terms
  "Restrictions. The device manufacturer or installer and Microsoft reserve all rights (such as rights under intellectual property laws) not expressly granted in this agreement and no other rights are licensed to you. For the avoidance of doubt, this license does not give you any right to, and you may not(and you may not permit any other person or entity to):"
  ...
  (vi) reverse engineer, decompile, or disassemble the software, or attempt to do so, except and only to the extent that the foregoing restriction is (a) permitted by applicable law; (b) permitted by licensing terms governing the use of open-source components that may be included with the software; or (c) required to debug changes to any libraries licensed under the GNU Lesser General Public License that are included with and linked to by the software; and
  ....
  """

  > Tehát még mindig tartom, hogy nem a nyíltság meg a zártság számít,
  > hanem az, hogy akik programozzák azok mennyire szakértők, segítőkészek, támogatóak.

  akkor eltér a véleményünk ..

  Mert ettől még önmagában kockázat a zárt kód ..
  és aki egyszer már megégette magát .. az óvatos lesz ..

  https://news.ycombinator.com/item?id=12518036
  https://web.archive.org/web/20160919001847/http://stephaniehurlburt.com/blog/2016/9/16/closed-source-engines-are-a-big-risk

  """
  (2016)
  In short, this was far from a vacation and in fact using Unity put the entire project at risk of not shipping. Developing in Unity involved months of hunting down obscure, black-box bugs that were fixed by switching versions, we had to trash weeks of work for this. It was not fun. It was well worth the high rates we charged. It didn't help that we're still in the early days of VR, I'm sure.
  It's the black box nature that's most troublesome to me. With source code, it's still a huge codebase that's hard to parse and has plenty of problems, but at least I can hunt down my bugs.
  This project was able to build up really quickly at first, but almost couldn't launch because of Unity issues. And this is with two engineers on the project with tons of engine and game development experience.
  I know not every project runs into this issue, but it made me never want to use Unity in production, ever. Prototypes are fine. Anything beyond that is a risk I don't need to take as a programmer perfectly capable of digging into the innards of engines.
  In production-quality projects I lead tech direction on, I will only use an engine with source access, or build my own. I can't take this risk.
  """

Új hozzászólás Aktív témák