What is Hackers' Pub?

Hackers' Pub is a place for software engineers to share their knowledge and experience with each other. It's also an ActivityPub-enabled social network, so you can follow your favorite hackers in the fediverse and get their latest posts in your feed.

0

Learn Haskell by example. ~ Phillip Hagenlocher. books.google.com/books?id=n38p

Learn Haskell by Example

Learn Haskell by doing Haskell projects! In this book, you��ll get practical experience writing Haskell code and applying functional programming to actual development challenges.In Learn Haskell by Example, you��ll build your Haskell skills by working through hands-on challenges and conundrums. You��ll learn to look at each project through a Haskell lens, and then solve it using features like lazy evaluation, immutable data structures, and monads. In Learn Haskell by Example you will learn how to: • Use Haskell for daily programming tasks • Effectively apply functional concepts • Avoid common beginner pitfalls of Haskell • Apply abstract concepts in the Haskell language • Debug and profile Haskell applications • Improve the performance of Haskell applications Haskell is an amazing choice for applications that need an extra guarantee of safety, such as in smart contracts, data intensive applications, and large scale distributed systems. In this book, you��ll see just how practical Haskell can be for creating programs by building your own engaging projects! Learn how to structure real-world applications, how to work with the Haskell tool chain effectively, and what to look out for when writing critical sections in the program's logic. Best of all, each project in this book is fully extensible and customizable so you can keep tinkering with your favorites! About the technology Programmers spend a lot of time debugging and refactoring code, reading comments and documentation, and trying to make sense out of complex designs. Haskell, a powerful, beautiful, and challenging functional programming language, promises a different path. By focusing your attention on simple functions, clearly-defined behaviors, and the right high-level abstractions, Haskell disallows the dangerous behaviors that usually lead to bugs and crashes. About the book Learn Haskell by Example teaches you to build applications in Haskell by designing and coding fun and engaging projects. In this easy-to-follow guide, you��ll create a domain specific language for music, an image processing library, and more! You��ll learn Haskell from the ground-up with a focus on important concepts like function design, composition, and data immutability. Each project gives you a new insight into how to think in Haskell and helps you understand why many Haskell developers say they will never use another language again. What's inside • Use Haskell for daily programming tasks • Purely functional programming • Avoid common Haskell pitfalls About the reader For readers who know how to program in an object-oriented language. About the author Philipp Hagenlocher is a full time Haskell developer, and the creator of the beloved Haskell for Imperative Programmers YouTube course. The technical editor on this book was Alexander Vershilov. Table of Contents 1 Introduction 2 Ancient secret keeping on modern machines 3 Every line counts 4 Line numbering tool 5 Words and graphs 6 Solving the ladder game 7 Working with CSV files 8 A tool for CSV 9 Quick checks and random tests 10 Digital music box 11 Programming musical compositions 12 Parsing pixel data 13 Parallel image processing 14 Files and exceptions 15 Transformers for synchronizing 16 JSON and SQL 17 APIs using Servant Appendix A The Haskell Toolchain Appendix B Lazy evaluation

books.google.com · Google Books

0
0
0
0
0
0

田中はもう三年近く行ってないけどその時にはもうジャブ漬けは無くなってた気がする
僕はガッツリ漬けたほうが好きで田中の衣は硬めなんだけど
今思えばあれはジャブ漬けしても衣が落ちないようにするためだったのでは
ジャブ漬けしないなら衣はもっと軽めにしたほうがいい気がする
まーどのみちもう全然行ってないんだけども

0
0
0
0
0
0
0
0

그동안(10+년;;) git이 엄청 잘만든 물건 같지는 않다고 생각하며 대충 쓰고있었는데, 요즘 branch 개념 자체가 근본적인 실수란 생각이 들기 시작했다. branch 대신에 변경의 시작과 끝, 양 끝점을 가지는 interval을 쓰는게 맞는거 같다(카테고리 이론의 작은 교훈: primitive는 양 끝점을 가지는게 좋다).

git을 쓰면 히스토리 길어진다고 squash merge 등을 하는데, (나도 하지만) 사실 기껏 만들어놓은 히스토리를 뭉개버리는 말도 안되는 동작이다. 만약 interval을 쓴다면 히스토리는 그대로 남기고 UI 단에서 fold/unfold 등을 해줄수 있을 것이다.

Darcs 등이 interval에 기초하는데, 지금은 일이 너무 바빠서 시도할 여유가 없다. 한번 숨고를 시간이 주어지면 멀쩡한 VCS를 탐색하는 시간을 가질것이다.

0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

nominally has the capacity to be decentralized, in practice, it's fully centralized. What led @vortexAdam Burns to call it "federation washing".

But what about ? Is this a working example of of Bluesky?

On the level of technical infrastructure, it's a service built on top of Bluesky, on a social level, it's clearly distinct (different feeds, moderation, social user basis).

In terms of building a space of a large minority community, it seems to have succeeded where Mastodon failed so far,. And it might even be large enough to decentralize the infrastructure as well.

privacy.thenexus.today/decentr

0
0
0

그동안(10+년;;) git이 엄청 잘만든 물건 같지는 않다고 생각하며 대충 쓰고있었는데, 요즘 branch 개념 자체가 근본적인 실수란 생각이 들기 시작했다. branch 대신에 변경의 시작과 끝, 양 끝점을 가지는 interval을 쓰는게 맞는거 같다(카테고리 이론의 작은 교훈: primitive는 양 끝점을 가지는게 좋다).

git을 쓰면 히스토리 길어진다고 squash merge 등을 하는데, (나도 하지만) 사실 기껏 만들어놓은 히스토리를 뭉개버리는 말도 안되는 동작이다. 만약 interval을 쓴다면 히스토리는 그대로 남기고 UI 단에서 fold/unfold 등을 해줄수 있을 것이다.

Darcs 등이 interval에 기초하는데, 지금은 일이 너무 바빠서 시도할 여유가 없다. 한번 숨고를 시간이 주어지면 멀쩡한 VCS를 탐색하는 시간을 가질것이다.

0
0
0
0
0
0
0
0
0
0

그동안(10+년;;) git이 엄청 잘만든 물건 같지는 않다고 생각하며 대충 쓰고있었는데, 요즘 branch 개념 자체가 근본적인 실수란 생각이 들기 시작했다. branch 대신에 변경의 시작과 끝, 양 끝점을 가지는 interval을 쓰는게 맞는거 같다(카테고리 이론의 작은 교훈: primitive는 양 끝점을 가지는게 좋다).

git을 쓰면 히스토리 길어진다고 squash merge 등을 하는데, (나도 하지만) 사실 기껏 만들어놓은 히스토리를 뭉개버리는 말도 안되는 동작이다. 만약 interval을 쓴다면 히스토리는 그대로 남기고 UI 단에서 fold/unfold 등을 해줄수 있을 것이다.

Darcs 등이 interval에 기초하는데, 지금은 일이 너무 바빠서 시도할 여유가 없다. 한번 숨고를 시간이 주어지면 멀쩡한 VCS를 탐색하는 시간을 가질것이다.

0

しかし生体認証を有効にしていると問答無用で身柄を取り押さえられたときに無力そうなのがなあ。iOSだと電源ボタンを5連打でTouch ID/Face IDを無効化できるけど、咄嗟に5連打なんて出来るかなあ。というかそこからフォレンジックツールで攻撃されることも想定するとさらに電源も切りたいところだし(お前は何と戦っているのか)

0
0
0
1
0
0
0
0

いつもお世話になっております。

サーバーの切り替えのため、これから15分ほど接続が不安定になる可能性がございます。

ご迷惑をおかけして申し訳ございませんが、何卒よろしくお願い申し上げます。

0