Search Ideas

I think the thing I’m really fighting here is Rails being object-oriented. Which I can’t do anything about.

Not sure the Rails team realizes how much OOP reduces the extensibility of Rails.

Having explored three different ideas, I believe #302 – having regular helper methods to render Hiccdown structures – is the best.

The idea is not without its flaws, but having to qualify a method name by, say, calling it idea_form instead of form is still better than manually having to pass the view context around all the time and not being able to trivially access instance variables.

So I’ll stick with #302 for now, which is the status quo already.

#327 applies here, too: no access to instance variables inside helper class methods.

That’s way too verbose.

Instance variables are not available inside the methods.

I’m trying this now. Having to prepend every invocation of a helper method with vc. is getting really old really fast.

Tested, it works. self does indeed point to the view_context in the helper. Verified by printing object_ids.

Maybe ‘Display’. ProductsDisplay

I don’t like the term ‘renderer’ yet. It’s too loaded with meaning, what with Rails already having a render method in controllers and another render method in views…

I don’t think that’s something people would do a lot, but they still easily could: ProductsRenderer.index(self)

Hiccdown methods should live in their own, separate modules. How about they are called ‘renderers’?

1
2
3
4
5

module ProductsRenderer
  def self.index vc, # …
    vc.some_helper_method
  end
end

That would be mixing class methods an instance methods in Rails helper modules, which typically only contain instance methods. Not idiomatic Rails usage.

If so, there might be a way to bind them to the view_context. Or I could definitely pass the view_context explicitly as the first parameter:

So instead of

1

@helper_module.instance_method(@action_name).bind_call(view_context)

I would do

1

@helper_module.send(@action_name, view_context)

And the parameter list of each Hiccdown method would start accordingly:

1
2
3
4
5
6
7
8
9

module ProductsHelper
  def self.index vc #, …
    vc.some_helper_method
  end

  def some_helper_method
    # …
  end
end

That isn’t a good idea because Hiccdown methods often share the same conventional names (index, show, etc), which can and does lead to conflict.

Clearly, a fetus without a nervous system can’t be sentient and thus can’t be a person, right?

It’s not considered a fetus until week 9, at which point the nervous system has already begun building.

The correct word to use here is ‘embryo’.

If an already-born person is deadly ill, that doesn’t mean you can kill them. Why should that be any different for an unborn person?

What happens if only one of two twins is non-viable but abortion would kill both?

I have addressed this issue separately – it’s a separate idea. #274

Appeal to the supernatural

The heartbeat has no particular epistemological or moral relevance.

Defensive force and security services are productive endeavors.

Retaliatory force is only part thereof, and defense involves the employment of scarce resources, thus economic principles apply. (Logan Chipkin)

If the government tries to step outside the free market, that’s tantamount to pretending there’s magically no scarcity for the government. But in reality, the government still has to attract talent to fill government jobs, pay that talent, and use scarce resources. If it tries this without the error-correction mechanisms the free market provides, it will do anything poorly.

Two people out in international waters, or in space, or anywhere else with no government, can still have consensual interactions. For example, they can decide to share a sandwich. That’s still consensual if neither party has a preference that arbitrarily steamrolls over the other.

There are already consensual interactions between people that are nonetheless unregulated. Sex, for instance.

#240

This seems like a response to another idea (presumably #230 and/or #232), rather than a top-level idea itself. I suggest you move this idea and break it up if necessary. Mark it as a criticism to whatever ideas you end up criticizing.

But first, familiarize yourself with the current state of the discussion. Ensure that you’re making new points. These sound like points others have made before you. Read the entire discussion before you continue. If these points are indeed duplicates, either think of new criticisms or address existing criticisms. Don’t repeat the same ideas if you can’t address preexisting issues with them.