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

help-circle



  • Lysergid@lemmy.mltoProgrammer Humor@programming.devLanguages
    link
    fedilink
    arrow-up
    5
    arrow-down
    1
    ·
    edit-2
    1 month ago

    Library built this way because it supposed to be flexible and provide ground for complex usecases. It can only be flexible if your API works with simple abstractions which you can then compose. It’s not driven by “I need this specific utility for this specific scenario”. That would be zoo you have in JS where you have 10 ways to iterate over array and 9 of them wrong for your scenario.

    Java’s OO is great because they design library with SRP in mind making sure there is few but good ways to do things.

    BufferedReader cannot accept file name because it makes arbitrary reader… well buffered. It’s not BufferedFileReader, even that would accept something like Path or File, not string, because File can be remote file, should Reader now know all possible local and remote protocols and path formats? What else it must do?

    Having it designed the way it is, allows Java to have utilities for various scenarios. Your scenario covered by standard lib too. See Files.readAllLines which, surprise-surprise, built on top of BufferedReader.













  • I don’t know. Maybe read article. It says „Korean military”. According to them stock Android with 3rd party security app is acceptable and has no security concerns. Article itself highlights that 3rd party security apps are inferior and security holes in Android OS are basically neglected by Korean military since they will be addressed in updates at some point.

    OS does not matter when approach to security so superficial. Judging by this article Korean military has less robust security practices than some banks.

    Everyone here talking about some hypothetical Android based custom OS built for Korean military which does not exist and it is not what Korean military doing. They are allowing stock Android OS with „security app”. Not surprised they are not building custom OS because it is economically idiotic idea. You need army of cyber security experts familiar with Android OS architecture that will review whole OS code and customize for military. Then you need to pen-test it and keep on doing it on each upstream OS update or fork it and maintain internally. Which is another can of worms coz you’ll need to make sure internal fork works fine with up-to-date versions of apps. Otherwise you just have dumb smartphone with higher risk of vulnerabilities in outdated apps. At this point as I said, just force sensitive staff to use dumb phone or internal landline.

    And don’t tell me “but Samsung is Korean they can do it for Korean military”. It doesn’t not change the fact that it will cost astronomical amount of money and time. Can Samsung do it? Probably yes. Will Korean military be able to offer enough money to probably the only local company that can do it which also has revenue of approx. 20% of Korea’s GDP. I doubt.