metapsj · HackerTrans

3 yıl öncediscuss

The Limits of the Singapore Housing Model https://marketurbanism.com/2020/08/05/the-limits-of-the-sing...

3 yıl öncediscuss

imho the key concept is in-process rest as in representational state transfer as an interface. instead of an imperative interface it's more of a protocol based interface. think http middleware built around a standard interface like ruby's rack, asp.net's owin, or python's wsgi. once you have that style of abstraction it becomes pluggable and you can chain them together.

here's a past discussion on in-process rest.

https://news.ycombinator.com/item?id=21560626

metapsj

3 yıl öncediscuss

You have to follow Marcel Weiher's work on combinators aka connectors.

The following article references his work on in-process rest, polymorphic identifiers, and storage combinators.

What Alan Kay Got Wrong About Objects

https://blog.metaobject.com/2019/11/what-alan-kay-got-wrong-...

Here's an ACM SIGPLAN talk he gave on storage combinators...

Storage Combinators @ SPLASH'19

https://www.youtube.com/watch?v=6FFlmkFS1YY

The ACM SIGPLAN talk is a very good starting place to get an understanding what he is talking about.

metapsj

3 yıl öncediscuss

here's a couple more to throw into the mix.

Hypertext allows you to write HTML from Ruby. https://github.com/soveran/hypertext

rbexy - A Ruby template language inspired by JSX https://github.com/patbenatar/rbexy

imho, hypertext has a great deal of potential especially the DSL.

metapsj

4 yıl öncediscuss

maximum employment is a pandemic period objective. they aren't intending to crush the labor market. the fed has largely behind the curve in addressing inflation.

metapsj

4 yıl öncediscuss

appreciate your response.

i get the impression dense urban environments are ripe for various types of capture not to mention the variety of competing interests that end up diluting the effectiveness of policy to address these issues.

also, i get the impression incentives for housing developers aren't aligned to addressing this problem because in the end it would mean lower margins and a smaller pipeline of future housing development projects effectively putting them out of business.

metapsj

4 yıl öncediscuss

are there other options besides increasing the density of housing?

metapsj

4 yıl öncediscuss

along the same line...

freemesh for wifi AP based mesh networks. not as convenient as briar, but considering the situation having multiple modes of communication seems like a good hedge.

  https://freemeshwireless.com/

also, if you can get a hold of lora wan based devices, e.g. esp32 w/ lorawan, you can set up a lorawan based mesh network with wifi entry points.

  https://meshtastic.org/

metapsj

5 yıl öncediscuss

hopefully you find this helpful...

On December 7th, 2016, Pebble announced that they were ceasing operations. Two days later, on December 9th, 2016, the Rebble web site went live, announcing our intention to "maintain and advance Pebble functionality, in the absence of Pebble Technology Corp." We have fulfilled much of this goal via Rebble Web Services, which restores most of the functionality that the Pebble community knows and loves.

https://rebble.io/

metapsj

6 yıl öncediscuss

can you elaborate on ruby? i'm curious to understand your experience with it and what brought you to the conclusion that you "hate programming".

metapsj

7 yıl öncediscuss

here's another option to throw into the mix...

ward cunningham's federated wiki https://wardcunningham.github.io/

metapsj

7 yıl öncediscuss

thx :-) i get the impression event sourcing for the uninitiated is too abstract a concept and is often confused with event-driven architectures.

metapsj

7 yıl öncediscuss

event sourcing and the notion of compensating transactions go along way in solving these types of problems.

metapsj

7 yıl öncediscuss

great for data that is mostly read intensive. not so great if you have lots of writes.

@maxk42 approach with the relationship table works well for both read and write intensive applications.

metapsj

7 yıl öncediscuss

great for data that is mostly read intensive. not so great if you want lots of writes.

@maxk42 approach with the relationship table works well for both read and write intensive applications.

metapsj

7 yıl öncediscuss

i don't have any experience with Stripe Atlas. here are the highlights of their offering.

Enables founders to assign relevant IP to the company at formation, formalizing ownership of key technology.

Is designed to make conversion to a C Corporation as simple as possible. (We can connect Stripe Atlas users to a lawyer to manage the conversion process with discounted, flat-rate packages).

Provides a simplified process for adding members after formation.

Is organized in Delaware, the jurisdiction of choice for many new LLCs.

https://stripe.com/blog/atlas-llc

metapsj

7 yıl öncediscuss

would it be a stretch to say criminally negligent? or conspiring to obstruct an active investigation? obviously it would require further investigating the back channel of communication within the company and the individuals involved, but in this day and age courts can request company emails and phone records.

metapsj

7 yıl öncediscuss

I think there's a middle ground, it's more a domain driven design centric view of the world. Each domain is a monolithic style application with services that run in their own processes and communicate via some type of messaging infrastructure e.g. postgres, redis, zeromq, etc. The critical aspect of this approach is well-defined message schemas and versioning. The services can be spun up with a Procfile or built into a container. As you move towards container based infrastructure, other services like instrumentation, monitoring, and aggregation of logs are required.

metapsj

8 yıl öncediscuss

i tried searching for the "Lucy ecosystem" in relation to C# and .Net but was not able to find any references to it. I'm guessing is an acronym for a stack, could you further clarify?

metapsj

8 yıl öncediscuss

physical limit is probably to narrow to effectively argue my original position. there are many limiting factors including physical boundaries of geography. consider the political climate, economic environment, accumulated technical debt of past construction practices, artificial boundaries development by cities to bolster real estate values, not to mention investments made by individual home owners and businesses. there are a lot of forces at play to gain consensus especially when you have significant momentum moving along a trajectory started easily 30 years ago that led us to where we are today. and not to mention the accumulated debt of a city like san francisco which the last i read was at $10B. these forces are like concrete or better yet non-newtonian in nature, the more you stir the pot the more rigid it becomes.

i agree there are a lot benefits to density, i'm not down playing those benefits. but i do think we have a lot of great technology in play and coming down the pipe that allows us to have many of the same benefits across large geographic areas.

also i feel large cities are captive to it's wealthy benefactors whether it's a company, an individual, or a politician who wields influence.

more importantly, it's far easier to create incentives to entice companies with high economic value and high paying jobs to an area with few competitive forces.

comments