Hacker Newsnew | past | comments | ask | show | jobs | submit | more BiteCode_dev's commentslogin

Also, it is suspected than Apple actually orchestrate those "leaks" for free publicity.


We live in a conspiracist society, any secret plan you can imagine has "been suspected", and generally people require no particular evidence other than "it would make sense to me" (as if there aren't plenty of things that would make sense to me that haven't happened!)

But if Apple actually wanted media outlets to cover it, having law enforcement seize and search the property of the editor that broke the story, and then banning the media outlet that broke it from WWDC... doesn't seem like the way to encourage anyone to cover it next time there's a leak, if you're actually hoping for coverage of secretly orchestrated leaks. https://www.pcmag.com/archive/gizmodo-banned-from-wwdc-25149...


Does Apple do controlled leaks? Of course, any company which is able to keep secrets in the first place does.

For the iPhone 4? Absolutely not, the only other model which changed iPhone as much as the 4 was the X, Steve was still alive for the 4 and there is absolutely no way he would have approved just leaving it in a bar for hype.

Steve Jobs wanted to be the person who showed that to the world. Remember the first MacBook Air? Steve lived for that moment.


[by whom?]



I suspect it, tbh


Yes, but authenticity as value signaling, not as a commitment to behave without unnecessary layers.

I lived in a meditation center for a year, and I saw some people there that claimed to be authentic, and worked to look like the stereotype. But they were actually hiding a desire for materialism and the failure to live up to it behind the apparent choice of rejecting it.

Irony can be pretty ironic.


I fear that we will get used to some image patterns feeling right instead of reality if AI gets involved too much.


You have the burden of responsibility, because you take it. Many people in charge don't and will gladly blame others as much as they can, yet get away with it because some management don't wish for integrity, but need a watchdog.


Yes, all the companies are rent seeking.

They don't want having to keep producing value to deserve the money, they want to just cash in, indefinitely, like nobles used to do.


Zulip is really underrated.

It's a chat app that doesn't eat your life, but just provides the service of helping you to communicate. It doesn't want to interrupt your workflow. It doesn't try to connect to everything. It makes it easy to organize work conversations and doesn't wish to be the remote work coffee machine.

It seems unreal that nowadays, I find solace in a software for finally trying to help me instead of extracting value or stealing attention from me. It should be the default.

Zulip is just that: the vlc of team chat.


My former company adopted Zulip because we were in the cybersecurity space and needed an on-prem solution. When I first saw it I thought "oh god this is going to be awful" - very ugly UI compared to Slack and others. But after getting used to it, I found that the UX is excellent.

For anyone searching around, don't be put off by the lack of "polish" - Zulip has a really good fundamental design.


When everyone on the team learn to use Topics, it's life changer.


And hence the general recommendation of having a single direction in your input/render cycle:

- wait for input

- a dispatcher take any input and turn it into a queue of model update actions

- pop queue to perform latest model updates.

- trigger a full tree rendering, passing the new model

- start again

So:

- the model is a dumb static data structure

- the dispatcher is the responsible for model updates and is a single entry point for the data flow

- the UI and the model don't know about each other

That what ELM, react and so on do now. Monodirectional MVC. It's hard to optimize the rendering though, but it's way easier to reason about when concurrency gets high.


> - trigger a full tree rendering, passing the new model

I agree the Elm model makes it easy to reason about it.

Just because we pass "the state of the world" each time instead of mutating it, does not mean that we need a full tree rendering. That is an implementation detail.

We can update just the relevant part. If we think of it mostly as pure functions a lot of it is easier to memoize and — for same input — it is possible to return the same output straight away.


That's what I mean by hard to optimize. Memoization is hard to get right, because if you compare only by value, it can be slow, but if you compare by identity, the cache can take a lot of memory.

And of course, forcing a purely immutable model comes with its own unique challenges.


Can't you just declare:

    my() {
  script_name="$1"
  script_path="$HOME/.local/bin/my/$script_name"
  shift
  $script_path "$@"
    } 
So you have your namespace ? Of course that mean you must put all script in .local/bin, not anywhere in the PATH, and some more work is needed to figure out completion.

But it seems less weird than the comma.

-- EDIT --

With completion:

export MY_SCRIPS_DIR="$HOME/.local/bin/my"

_my_completions() {

   if [ "${#COMP_WORDS[@]}" != "2" ]; then
     return 
   fi

   COMPREPLY=($(compgen -W "$(echo $(find "$MY_SCRIPS_DIR" -printf '%P\n' ))"))
 }


 my() {
  script_name="$1"
  script_path="$MY_SCRIPS_DIR/$script_name"
  shift
  $script_path "$@"
 } 

 complete -F _my_completions my
-- EDIT 2 --

After testing both, the comma win. Kiss, more flexible.


5 times a year if you are a freelancer.


Linux already stores plenty of secrets in files in /etc. Just do the same: the root protected init file for your app likely has a mechanism for passing an env var to the new process. Systemd and supervisor do. Then pop os.environ instead of reading it, and you are safe from bots and script kiddies, which is likely your threat model


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: