-
Seriously? Where is emacs?
-
It’s still recovering from Kyle Machulis’s loving.
-
-
-
Is there a modern version of this that works across a bunch of lisp installs?
-
-
Clisp’s implementation notes claim that there is an upper bound:
BIGNUMs are limited in size. Their maximum size is 32*(2^16-2)=2097088 bits. The largest representable BIGNUM is therefore 2^2097088-1.
-
-
-
Is this just a frontend for graphviz?
-
No, it’s its own system. I used it for a while for flowcharts and sequence diagrams at work, and it does the job okay. The main benefit over graphviz is that it’s way easier to learn and can be embedded in markdown more easily. But if you want anything more complicated than a flow, or you want any control over the weights, you’re stuck with graphviz.
-
-
-
-
It’s straightforward to set up OpenVPN to do this with systemd and a script.
Personally I use it from home too. My ISP doesn’t need to know my business.
-
You correctly advised people to use great books like Practical Common LISP to learn the gotchas of that. Another I saw in Barnes and Noble that looked fun was Land of LISP. I just skimmed it so can’t say how good it is past fun examples can keep people motivated to learn.
When you brought up Scheme and Racket, you didn’t mention the de facto book How to Design Programs that most Racket users tell me they learned from. It gets mentioned in about every discussion on Scheme or Racket plus many on programming in general. Did you try going through that book with Racket and still had the problems you mentioned? If not, maybe try HtDP. If so, maybe mention it anyway since it does help a lot of people learn Scheme. The combo of that plus your own experiences would then let people know they might have better luck with Common LISP if Scheme doesn’t work out.
And welcome to Lobsters! Hope you enjoy it. :)
-
-
Thanks @nickpsecurity
I’m not the author of the blog posting. Just thought it would be of interest here.
In fact I agree with your comments on the article. As it happens I teach the students at my university Racket as their first language. A large part of the course is based on HtDP.
-
Oops. I looked at it wrong. Good you are already on top of the HtDP thing. :)
-
-
While I think a website like this would make sense in a few years, right now I think GDPR is complicated, confusing, and scary enough to a lot of companies that they are going to make mistakes. I’d rather help them do it better than mock them.
As one of the thousands of engineers who had to figure out how to shoehorn a six-month compliance project into a lean team’s packed roadmap, I concur. This wasn’t easy, not even at a company that respects user data to begin with. Lots of the jokes I’ve seen about GDPR right now just lessen my opinion of the teller.
On the other hand, we’ve all had literally more than 2 years to work on said six-month compliance project, and the fact that so many companies try to push on until the very end to start working on it is the actual problem here IMO.
Not from my point of view – who cares if companies just woke up to GDPR two weeks ago, if I don’t use them for data processing? None of my actual pain came from that. But I definitely spent a lot of time working on GDPR when I’d rather have been building product, other deadlines slipped, things moved from To-Do to Backlog to Icebox because of this. We’re ready for GDPR, but that stung.
I was essentially trying to put “People like you don’t get to complain about it being hard to fit something into a certain time period when they had literally 4 times that amount of time to do it.” ^__^
Well, if people like you (who didn’t even do the work) get to complain, then so do I! If someone tells me they’re gonna punch me in the face, then they punch me in the face, I still got punched in the face.
I did our GDPR planning and work, and I’m so glad to see it in effect. The industry is finally gaining some standards. Sometimes it’s time to own-up that you care more about your own bottom-line than doing the right thing, if you complain about having to give up a “rather have been building product” attitude.
Sometimes if you don’t build a product, GDPR compliance becomes irrelevant because you never get a company off the ground. As a one-person platform team until last September, I don’t regret how I prioritized it.
I actually did do the work. But either way, complaining about it being a pain overall is just fine, because it is. On the other hand, explicitly complaining that because you had to do it in 6 months you had issues fitting it in, had other deadlines slip, and had to essentially kill other to-do’s is a very different thing. If you’d used the extra 18 months, I bet you’d have had much less issues with other deadlines.
This analogy doesn’t even make sense in context…
I’ll totally remember this for next time.
Well, I agree in general, but this article specifically highlights some cases of just plain being mean to your users. I’m okay with mocking those.
I disagree. GDPR is expensive to get wrong so the companies aren’t sure what to expect. They are likely being conservative to protect themselves.
They were not conservative in tracking users, and spending for tracking and spying on users was not expensive?
As a user I don’t care about the woes of companies. They forced the lawmakers to create these laws, as they were operating a surveilance capitalism. They deserve the pain, the costs, and the fear.
Tracking users is very cheap, that’s why everyone can and does do it. It’s just bits.
Feel free not to use them, then. What I am saying is that GDPR is a new, large and expansive, law with a lot of unknowns. Even the regulators don’t really know what the ramifications will be. I’m not saying to let companies not adhere to the law, I’m just saying on the first day the world would probably benefit more from helping the companies comply rather than mocking them.
EDIT:
To be specific, I think companies like FB, Google, Amazon, etc should be expected to entirely comply with the law on day one. It’s smaller companies that are living on thinner margins that can’t necessarily afford the legal help those can that I’d want to support rather than mock.
It’s not like the GDPR was announced yesterday. It goes live tomorrow after a two year onboarding period.
If they haven’t got their act in order after two years, it’s reasonable to name and shame.