HackerTrans
TopNewTrendsCommentsPastAskShowJobs

cwp

no profile record

comments

cwp
·geçen ay·discuss
He lost me at "our particular moment of dystopian late capitalism."
cwp
·6 ay önce·discuss
This article is drivel. If a supplier writes down the value of a contract with Tesla, they're saying Tesla is buying fewer batteries, or will in the near future. That is, there is a lack of demand for the batteries. If you're determined to take this as bad news for Tesla, rather than bad news for L&F, you could maybe speculate about lack of demand for Cybertrucks, but spinning it as "supply chain collapse" is just silly.
cwp
·9 ay önce·discuss
The code example is very similar to Ray.

Monarch:

  class Example(Actor):
     @endpoint
     def say_hello(self, txt):
         return f"hello {txt}"

  procs = this_host().spawn_procs({"gpus": 8})
  actors = procs.spawn("actors", Example)
  hello_future = actors.say_hello.call("world")
  hello_future.get()
Ray:

  @ray.remote(num_gpus=1)
  class Example:
      def say_hello(self, txt):
          return f"hello {txt}"

  actors = [Example.remote() for _ in range(8)]
  hello_object_refs = [a.say_hello.remote("world") for a in actors]
  ray.get(hello_object_refs)
cwp
·6 yıl önce·discuss
Not that important, at least in the SV-centred tech world. I have a journalism degree, and I don't think it's ever been a problem. I've also been a hiring manager, and on hiring committees and never really paid much attention to it. Degrees matter in data science but not software engineering.
cwp
·7 yıl önce·discuss
Well, the environment isn't the only factor, but it's the biggest one. You have to take care of routing, permissions, timeouts, errors etc on the server as well. Data being "an sql query away" on the server is similar to being "an AJAX call away" on the client.

If you have a UI, you're going to have to manage UI state somewhere. Even if you have no client-side code, you've marshal that state into strings to send to the client, and then parse it all out again on the server when you get the next request. Remember hidden form fields? Heck, this very site has some pretty interesting history about attempts to solve that problem elegantly. It was a PITA.

Ultimately, none of that has to do with Javascript; it's inherent in a client-server architecture. The one thing that is specific to JS is asynchronicity. If you don't like that, ok, fair enough, but that's a matter of taste. It has advantages as well as disadvantages, and with Promises and async/await, it's actually pretty elegant. It's certainly not the case that asynchronicity makes you write shit code.
cwp
·7 yıl önce·discuss
It's not Javascript that makes you write shit software. It's trying to write software that runs correctly on a wide variety of platforms that you don't control.

reaperducer's rewrite was an improvement, not because he replaced Javascript with PHP, but because he moved all the logic to the server, which is a single environment he controls. He could have used Node instead of PHP and achieved the same thing.
cwp
·16 yıl önce·discuss
Look up the meaning of "innovation." It's not the same as "invention." Innovation is when you take an invention and make it practical. That is, bring it to market in a product that has a significant impact. Apple has surely done this many times.